<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - MegaChips MCDP2800 LSPCON and ASRock Fatal1ty Z170 Gaming-ITX/ac issues (Broadcast RGB, HDMI output, triple monitor not working)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94248#c95">Comment # 95</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - MegaChips MCDP2800 LSPCON and ASRock Fatal1ty Z170 Gaming-ITX/ac issues (Broadcast RGB, HDMI output, triple monitor not working)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94248">bug 94248</a>
from <span class="vcard"><a class="email" href="mailto:nw9165-3201@yahoo.com" title="nw9165-3201@yahoo.com">nw9165-3201@yahoo.com</a>
</span></b>
<pre>(In reply to Ville Syrjala from <a href="show_bug.cgi?id=94248#c94">comment #94</a>)
<span class="quote">> That "infoframes: 0" part is telling me that your display likely doesn't
> identify itself as supporting HDMI, so we treat it as DVI and decide to send
> it full range data instead of limited range data.</span >
It _is_ a DVI monitor. It's connected via a passive HDMI to DVI-D cable (HDMI
on the PC side, DVI-D on the monitor side).
<span class="quote">> But for DP (which is what
> LSPCON is for us) we don't make that distinction. Unfortunately the DP spec
> doesn't make any useful provisions for these kinds of combinations. so we're
> basically left to guess what we should be doing.
>
> I think what we might want to do is send full range data regardless of the
> timings when dealing with a DVI/HDMI downstream port and the monitor doesn't
> identify itself as HDMI compatible (essentially using the same logic as we
> use for native HDMI). DP++ downstream port might more difficult since I
> don't recall if we can somehow tell if the plugged in monitor is actually
> DVI/HDMI or DP (I'll need to look into this a bit more). For
> VGA/NO_EDID/whatnot downstream ports sending full range all the time might
> be the right choice.</span >
Please simply remove the automatic detection. No one wants it anyway, see:
<a href="https://bugzilla.kernel.org/show_bug.cgi?id=94921">https://bugzilla.kernel.org/show_bug.cgi?id=94921</a></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>
</ul>
</body>
</html>