<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [hsw Color] Intel Haswell GPU HD4400 has wrong color management on external screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=82829#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [hsw Color] Intel Haswell GPU HD4400 has wrong color management on external screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=82829">bug 82829</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 <a href="show_bug.cgi?id=82829#c9">comment #9</a>) > We do this with Broadcast RGB Automatic because DPv1.2 says, "When a Source > device is transmitting a RGB stream with a video timing format called out in > CEA-861C Section 5 as using CEA range RGB, it must use the CEA range RGB." > > However it also says, "However, a Source device may transmit all code values > from zero to the maximum even when it declares the CEA range in the Main > Stream Attributes. It is the responsibility of the Sink device to limit the > pixel value > range as needed." > > I wonder if we could do that. Ville? My interpretation of the latter clause is that the source is allowed to include "invalid" pixel values in the data and the sink must be ready to receive them and clamp them to the limited range. So if we would send full range data and tell the sink it's limited range the sink will just clamp it and you get the "crushed blacks" syndrome. I really wonder how so many display get away with ignoring the spec. I can only assume that the compliance tests don't check for this issue, and thus you can get the DP sticker on your product even if it doesn't do as the spec says.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>