<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [IVB] 12bpc hdmi causes wrong real refresh rate (swapbuffers return time)" href="https://bugs.freedesktop.org/show_bug.cgi?id=93361#c28">Comment # 28</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [IVB] 12bpc hdmi causes wrong real refresh rate (swapbuffers return time)" href="https://bugs.freedesktop.org/show_bug.cgi?id=93361">bug 93361</a> from <a class="email" href="mailto:kevmitch@gmail.com" title="Kevin Mitchell <kevmitch@gmail.com>"> Kevin Mitchell</a> <pre>(In reply to Stanislav Lisovskiy from <a href="show_bug.cgi?id=93361#c27">comment #27</a>) > What about this bug? Should we now proceed with DRM property for explicit > 12bpc disabling for such case, so that there is at least no need in hacking > the EDID data? > Or as I understand there is an option to implement a clock bending, which is > order of magnitude higher in complexity. It sounds like clock bending is the proper fix. As you can see from the table in the description, the refresh rate can be wrong even without the 12bbc complications. 12bpc just makes it more wrong. That said, it would be nice to have some user control over 12bpc behaviour in the interim.</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> </ul> </body> </html>