[Bug 94248] MegaChips MCDP2800 LSPCON and ASRock Fatal1ty Z170 Gaming-ITX/ac issues (Broadcast RGB, HDMI output, triple monitor not working)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Jan 26 14:58:00 UTC 2017


https://bugs.freedesktop.org/show_bug.cgi?id=94248

--- Comment #95 from nw9165-3201 at yahoo.com ---
(In reply to Ville Syrjala from comment #94)
> 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.

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).

> 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.

Please simply remove the automatic detection. No one wants it anyway, see:

https://bugzilla.kernel.org/show_bug.cgi?id=94921

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170126/4b3daaaf/attachment.html>


More information about the intel-gfx-bugs mailing list