<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - 24bpp (True Color) limited RGB fix for Intel Graphics over DisplayPort"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107476#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - 24bpp (True Color) limited RGB fix for Intel Graphics over DisplayPort"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107476">bug 107476</a>
from <span class="vcard"><a class="email" href="mailto:nicholas.stommel@gmail.com" title="Nicholas Stommel <nicholas.stommel@gmail.com>"> <span class="fn">Nicholas Stommel</span></a>
</span></b>
<pre>My apologies, this indeed seems to be the case in the VESA documentation. But I
am unsure why the function call "drm_default_rgb_quant_range(adjusted_mode)"
seems to always return the value corresponding to
"HDMI_QUANTIZATION_RANGE_LIMITED" on every DisplayPort connector of each
monitor I try. That is perhaps the real question. I get the code conforms to
spec, what I don't get is why I always end up with washed out limited RGB when
I should be getting full RGB. It's not my computer, it has native DP 1.2 ports
connected to the HD 630 i7-7700 iGPU. I seem to be experiencing the same
problem as others in this active bug report
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL] LSPCon and DisplayPort always output limited range RGB, even when it should output full range RGB"
href="show_bug.cgi?id=100023">https://bugs.freedesktop.org/show_bug.cgi?id=100023</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>