<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HD4600] DVI does not support dual-link" href="https://bugs.freedesktop.org/show_bug.cgi?id=75345#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HD4600] DVI does not support dual-link" href="https://bugs.freedesktop.org/show_bug.cgi?id=75345">bug 75345</a> from <a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> Ville Syrjala</a> <pre>Created <a href="attachment.cgi?id=94640" name="attach_94640" title="drm/i915: Reject >165MHz modes w/ DVI monitors">attachment 94640</a> <a href="attachment.cgi?id=94640&action=edit" title="drm/i915: Reject >165MHz modes w/ DVI monitors">[details]</a> <a href='page.cgi?id=splinter.html&bug=75345&attachment=94640'>[review]</a> drm/i915: Reject >165MHz modes w/ DVI monitors I think the real bug here is getting a black screen because we fail to filter out the modes requiring dual-link operation. I think this patch should fix it. I'm not sure if we should additionally reject such modes when the HDMI VSDB indicates that the monitor support dual-link DVI. The spec seems to leave open the possibility of supporting both dual-link and >165MHz over a single link, and there's no way to tell the difference between monitors that do that, and monitors that only support higher pixel clocks through dual-link DVI.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>