<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><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> changed
<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="https://bugs.freedesktop.org/show_bug.cgi?id=100023">bug 100023</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>mkopec12@gmail.com, nw9165-3201@yahoo.com
</td>
</tr></table>
<p>
<div>
<b><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="https://bugs.freedesktop.org/show_bug.cgi?id=100023#c26">Comment # 26</a>
on <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="https://bugs.freedesktop.org/show_bug.cgi?id=100023">bug 100023</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>I am having this same issue, I believe the report I filed for DP on True Color
displays in <a class="bz_bug_link
bz_status_NEW "
title="NEW - 24bpp (True Color) limited RGB fix for Intel Graphics over DisplayPort"
href="show_bug.cgi?id=107476">bug #107476</a> is very similar to this bug report I found afterwards.
(In reply to Michał Kopeć from <a href="show_bug.cgi?id=100023#c21">comment #21</a>)
<span class="quote">> DisplayPort output defaults to 16-235 color range, while any other outputs
> on the laptop will correctly output 0-255 full RGB. There is currently no
> way to set the driver to default to Full RGB regardless of what the display
> EDID is.</span >
Michal's comment sums up exactly what is currently happening.
(In reply to N. W. from <a href="show_bug.cgi?id=100023#c8">comment #8</a>)
<span class="quote">> That being said: Please just fix
> <a href="https://bugzilla.kernel.org/show_bug.cgi?id=94921">https://bugzilla.kernel.org/show_bug.cgi?id=94921</a> instead of closing it
> without listening to your customers and the other issue will solve itself.</span >
I wholeheartedly agree with N.W. that something more needs to be done about
<a href="https://bugzilla.kernel.org/show_bug.cgi?id=94921">https://bugzilla.kernel.org/show_bug.cgi?id=94921</a>
However, my experience with Intel has been similar to Tom Yan's on
<a href="https://bugzilla.kernel.org/show_bug.cgi?id=94921">https://bugzilla.kernel.org/show_bug.cgi?id=94921</a> and to N.W.'s on this bug
thread. I don't think our concerns are really being taken into account here,
and personally I feel like my failed attempts to figure out what precisely is
going wrong were unkindly and summarily dismissed. I would greatly appreciate
if Intel could take this issue more seriously and propose some kind of fix
instead of threatening to close the issue entirely again.
This is not a personal matter or an attack on Intel graphics developers, nor
should it be treated as such. There is objectively something wrong when every
DisplayPort output connector powered by Intel integrated graphics defaults to
washed-out, limited 16-235 color on modern full range color displays. This
issue is mainly about general usability of Intel graphics over DisplayPort on
Linux, which likely affects far more users than the few of us who dug deep
enough to find this bug report here.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>