<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [sdvo lvds regression] "Use &intel_sdvo->ddc instead of intel_sdvo->i2c for DDC"" href="https://bugs.freedesktop.org/show_bug.cgi?id=65524#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [sdvo lvds regression] "Use &intel_sdvo->ddc instead of intel_sdvo->i2c for DDC"" href="https://bugs.freedesktop.org/show_bug.cgi?id=65524">bug 65524</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>Spec says clearly that the sdvo signal must be at least 100MHz, and at least the two sdvo encoders I have here (one DVI, other HDMI) have no issues with the low-res modes. My pet theory here is simply that this board/sdvo encoder combination has a problem with 4x pixel multiplier mode and the firmware engineer "fixed" this by frobbing the mode in the vbt a bit to push it over 50MHz dotclock. We could test this if you force the 4x mutliplier on the vbt mode, sdvo dotclock should be in the range 100-225MHz iirc, so it should still work.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>