<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [DP MST + DP-HDMI] DisplayPort always defaults to incorrect limited-range RGB on FullHD external display" href="https://bugs.freedesktop.org/show_bug.cgi?id=108821#c25">Comment # 25</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [DP MST + DP-HDMI] DisplayPort always defaults to incorrect limited-range RGB on FullHD external display" href="https://bugs.freedesktop.org/show_bug.cgi?id=108821">bug 108821</a> from <a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> Ville Syrjala</a> <pre>(In reply to Ivan Vlk from <a href="show_bug.cgi?id=108821#c24">comment #24</a>) > Can I expect this patch to be applied also to actual kernel stable branch, > please? Might require a bit of wrangling but should be doable. > More info about the RGB range: > > Mode is still Automatic, but RBG range is properly detected now. What really > surprised me is, that we I had "Full" mode before and that is what caused > very problematic color ranges. Now it's defaults to Limited and all seems > pretty normal again. > > So, finaly, the problem was not unreachable Full range, but unreachable > Limited range. Why the colors are such blurry in Full mode, that's another > question for another topic (or ranges has inverted names by mistake?) The usual symptoms of a mismatch are: * source limited range + sink full range: shades of black become light gray and bright shades aren't quite as bright as they should be * source full range + sink limited range: shades of black get crushed to fully black and bright shades get saturated to full brightness</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>