<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [HSW] i915 only uses 165MHz for HDMI port" href="https://bugs.freedesktop.org/show_bug.cgi?id=98491#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [HSW] i915 only uses 165MHz for HDMI port" href="https://bugs.freedesktop.org/show_bug.cgi?id=98491">bug 98491</a> from <a class="email" href="mailto:karolherbst@gmail.com" title="Karol Herbst <karolherbst@gmail.com>"> Karol Herbst</a> <pre>(In reply to Karol Herbst from <a href="show_bug.cgi?id=98491#c23">comment #23</a>) > (In reply to Jani Nikula from <a href="show_bug.cgi?id=98491#c22">comment #22</a>) > > I'm inclined to go with WONTFIX. The reasoning is that while this is > > annoying to you, you do get something on screen. Erring on the side of > > allowing >165 MHz modes when the display or link is not capable, one gets a > > black screen, which is arguably a worse outcome. Additionally, you have the > > workaround of adding the modes yourself. > > > > Ville, anything you want to add? > > Would it be possible to add a module parameter to overwrite the detected > limit? this way the user has an easier way to get those modelines, because > the alternative would be to enable drm debugging and fetch those modelines > and adjust the output so that xrandr accepts it. something like "i915.dspclkovwr=HDMI2=300" I don't know if those xrandr port names are already known in the driver at that time or not.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>