<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Wrong max TMDS clock rate on ThinkPad W541 mini-DisplayPort output" href="https://bugs.freedesktop.org/show_bug.cgi?id=107585#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Wrong max TMDS clock rate on ThinkPad W541 mini-DisplayPort output" href="https://bugs.freedesktop.org/show_bug.cgi?id=107585">bug 107585</a> from <a class="email" href="mailto:Simon80@gmail.com" title="Simon <Simon80@gmail.com>"> Simon</a> <pre>Wow! I made patches to implement the behaviour I described, but only after doing so did I notice that the kernel sees a value of 0x0 in the HDMI max data rate field. After digging a little deeper, I found this commit[1], which probably explains the discrepancy, and closes the door on a fix involving the VBT, at least for hardware equivalent to my system's configuration. As a last-ditch attempt to be friendlier to users, I'd propose at least making an educated guess about the maximum TMDS clockrate based on which generation of Intel Graphics chipset is driving the port. [1] <a href="https://cgit.freedesktop.org/xorg/app/intel-gpu-tools/commit/?id=5a17ee2c8f9013f5db852d27564b837f9f2c5a9f">https://cgit.freedesktop.org/xorg/app/intel-gpu-tools/commit/?id=5a17ee2c8f9013f5db852d27564b837f9f2c5a9f</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>