Re: [PATCH 4/4] fbdev: Convert a few drivers to use the fb_find_best_display helper

[Benjamin Herrenschmidt <benh@kernel.crashing.org>]

> My experience though is the contrary.  I find that if the edid has
> detailed timings and the 'prefer first detailed timing' flag is set,
> the detailed timings are reliable even on CRT displays.
> 
> However, there are buggy edid blocks where the flag is set, but there
> are no detailed timings at all, and that's when I get garbage.  (I already
> sent a patch that fixes these buggy edid blocks).

Ok, it may have been these then, I remember issues with some IBM CRTs a
while ago :)

>And still, there are edid blocks where they enumerate detailed timings
> but does not set the flag. This should not present with problems though.
> 
> Anyway, if there are such bad edid's out there, it's good if users refer
> them to the list so I can add them to the monitor blacklist database (we
> already have that in fbmon.c which currently has 2 entries). Anyway,
> users can always override the chosen default mode if it does not work
> for them.

Ben.




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click