<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Weird colours on usb-c to hdmi output" href="https://bugs.freedesktop.org/show_bug.cgi?id=99137#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Weird colours on usb-c to hdmi output" href="https://bugs.freedesktop.org/show_bug.cgi?id=99137">bug 99137</a> from <a class="email" href="mailto:daniel.blueman@gmail.com" title="Daniel J Blueman <daniel.blueman@gmail.com>"> Daniel J Blueman</a> <pre>I can reproduce the colour issue on 4.10-rc2 also, but the xrandr "Broadcast RGB" or 800x600 workarounds above don't work for me. I can't reproduce the issue on Windows 10 though, so the hardware validates. I find the adapter I use *does* give correct colours on my 1920x1080 projector, which reports 12-bit colour depth is in use from the menu. The other devices (including Dell U2713HM monitor) report only 8-bit colour depth in their EDID, so I bet the root-cause is either we are still sending 12 BPC data and should send 8 BPC, or we send 8 BPC but should be sending 12 BPC, and the adapter will truncate the data accordingly. Would disabling the EDID check leading to "clamping display bpp (was 36) to EDID reported max of 24" be a useful test?</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 assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>