Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Jun 2020 11:02:02 -0700
From:      Oleksandr Tymoshenko <gonzo@freebsd.org>
To:        rgrimes@freebsd.org
Cc:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r362029 - head/sys/dev/hdmi
Message-ID:  <20200611180202.GA56927@bluezbox.com>
In-Reply-To: <202006111344.05BDiwc4060074@gndrsh.dnsmgr.net>
References:  <202006102138.05ALcZZV087863@repo.freebsd.org> <202006111344.05BDiwc4060074@gndrsh.dnsmgr.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Rodney W. Grimes (freebsd@gndrsh.dnsmgr.net) wrote:
> > Author: gonzo
> > Date: Wed Jun 10 21:38:35 2020
> > New Revision: 362029
> > URL: https://svnweb.freebsd.org/changeset/base/362029
> > 
> > Log:
> >   Fix reading EDID on TVs/monitors without E-DCC support
> >   
> >   Writing segment id to I2C device 0x30 only required if the segment is
> >   non-zero. On the devices without E-DCC support writing to that address
> >   fails and whole transaction then fails too. To avoid this do
> >   not attempt write to the segment selection device unless required.
> >   
> >   MFC after:	2 weeks
> 
> Is it possible that this bad write is what has caused me to corrupt
> the EDID of 3 monitors over the last year while using a Display
> Port to HDMI cable on them?

Very unlikely. This write just sets segment index for the following
EDID read. 

Also the driver is used only on iMX6 and MIPS Creator CI20.

-- 
gonzo



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200611180202.GA56927>