<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [HSW] no modes bigger than 1080p in the parsed EDID for 4k TV on both HDMI/VGA" href="https://bugs.freedesktop.org/show_bug.cgi?id=67030#c33">Comment # 33</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [HSW] no modes bigger than 1080p in the parsed EDID for 4k TV on both HDMI/VGA" href="https://bugs.freedesktop.org/show_bug.cgi?id=67030">bug 67030</a> from <a class="email" href="mailto:damien.lespiau@gmail.com" title="Damien Lespiau <damien.lespiau@gmail.com>"> Damien Lespiau</a> <pre>I'm updating my sandybridge machine to be able to compile an X server easily, will take a while. At the moment I'm suspecting xf86ProbeOutputModes() that uses xf86ForEachDetailedBlock() to, it seems, compute max_clock from the DS_RANGE sections. On this EDID, we have a GTF range section: - Monitor ranges (GTF): 49-76Hz V, 15-80kHz H, max dotclock 140MHz and that ends up being used. I don't see any evidence that the X server parses the HDMI vendor specific block (other than xf86MonitorIsHDMI()) and that block contains a different max clock: - Maximum TMDS clock: 300MHz</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>