On Tue, Jul 26, 2011 at 10:52 AM, Alex Deucher <alexdeucher@xxxxxxxxx> wrote: > On Tue, Jul 26, 2011 at 9:20 AM, Dave Airlie <airlied@xxxxxxxxx> wrote: >> On Thu, Jul 7, 2011 at 3:01 PM, Alex Deucher <alexdeucher@xxxxxxxxx> wrote: >>> On Wed, Jul 6, 2011 at 7:30 PM, <reimth@xxxxxxxxxxxxxx> wrote: >>>> From: Thomas Reim <rdratlos@xxxxxxxxxxx> >> >> Guys I really still hate this :-) >> >> Other OSes must deal with this sort of thing and I can't say they >> don't do it like this but I can't say for certain this feels like the >> right answer. >> > > I emailed the closed driver display team, but as the issue seems to > only afflict certain rs690/rs740 boards, I'm not sure anyone will > remember what quirks those boards had as they are about 5 generations > old at this point. Another possibility is that the closed driver uses the hw i2c engine which may not be affected, or they just tell the hw i2c engine to fetch several bytes and they inspect the result similar to what this patch does. I'll let you know what I hear back. > >> My thinking is that we could probably just trust the hot plug detect >> if its reported on HDMI and DVI-D connectors, we still need to poll >> DVI-D as the VGA->DVI convertors don't often assert hpd. >> >> Am I missing something that this wouldn't fix? > > The issue in this case is that the problematic connectors don't have > HPD pin wired up and the ddc lines seem to be wired improperly so a > ddc probe always reports something connected unless you actually look > at the EDID header. For DVI-I we probably have to poll since only the > digital portion will assert hpd in most cases. > > Alex > _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
