Re: [Linux-fbdev-devel] [PATCH] nvidiafb: allow ignoring EDID info

[Giuseppe B. <giu...@gm...>]

On 2/22/07, Antonino A. Daplas <ad...@gm...> wrote:
> On Wed, 2007-02-07 at 00:08 +0100, Giuseppe Bilotta wrote:
> >
> > As mentioned in another post in this thread, I can't get any info out
> > of the i2c busses, because even when I have them available (i.e. after
> > loading nvidiafb) I get XXXX all around (on all three of them).
> > Suggestions on how to get the information welcome.
>
> Is this the same monitor you posted here?
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=112807065616218&w=2
>
> If yes, we already have the manufacturer and model code. The main
> problem is that the EDID of this display has no sync range (H: 75-75kHz
> and V: 60-60Hz).  Extending Hsync from 30-75kHz as a fix to the EDID
> block shouldn't be too hard.

Yes, that's it! Jeepers, I can't believe that even re-reading the past
LKML posts (even those!) I couldn't find the EDID info and how we had
gotten them. I guess I need stronger glasses.

Wonder why Luca's proposed patch makes the EDID undetectable, now, and
why can't it be retrieved at a later time via i2c. Timeouts too small?

> I already have a patch for this which I forgot to send to you
> before :-).  If you can confirm that this is still the same hardware,
> I'll send you a test patch

Yes, it's the same hardware. I can try the patch, with or without Luca's.


-- 
Giuseppe "Oblomov" Bilotta