![]() | ||||||||||
Messages in this thread |
On Sat, 01 Oct 2005 18:49:08 +0800, Antonino A. Daplas wrote: > Giuseppe Bilotta wrote:>> On Sat, 01 Oct 2005 13:49:59 +0800, Antonino A. Daplas wrote: >> >>> Looks like the nv driver just ignored the EDID and used one of >>> its built-in VESA modes. If you notice, X's EDID ouput is the same >>> as nvidiafb's. But the resulting timings are different. >>>>>> In contrast, nvidiafb will attempt to use the EDID, and only as a last >>> resort, use one of the timings in the global mode database.>> >> I see. And when EDID is enabled for the module, it won't let me touch >> those timings at all.> > Yes. But if the EDID block specified a usable hsync and vsync range, the > timings can be customized. In your case it does not. /me is wondering if it would be possible to hack the EDID block and fix it ... and whether it's worth the risk. >> Maybe a "noddc" or "noedid" module option for >> when EDID support is compiled in and one wants to work without it?> > It is a good idea. Especially since I've already encountered a lot of > crappy EDID blocks. That'd be nice :) Thank you very much for all your help and information. I can now exploit my eye-destroying 133dpi in console too :) -- Giuseppe "Oblomov" Bilotta "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-10-02 15:16 [from the cache] ©2003-2008 | ||||||||||