[Bug 107476] DisplayPort always defaults to incorrect limited-range RGB on Intel Graphics for 24bpp+ displays

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from Nicholas Stommel <nicholas.stommel at gmail.com> ---
(In reply to Rodrigo Vivi from comment #3)
> Nicholas, on that other bugzilla entry you mentined that with same monitor,
> same machine the ranges are differente with different connectors (DP vs
> HDMI), right?
> If, so, could you provide logs of both cases?

Rodrigo, thank you for your consideration and for moving the discussion here,
as I agree the primary issue is related to incorrect automatic range detection
for DisplayPort. Yes, you are right: on the same machine, HDMI range detection
works correctly on every display I have tried, but never works correctly with
DisplayPort (on Linux, I should add. Intel's Windows drivers always correctly
select full-range RGB over DisplayPort for the displays I have tried).

Michal's comment from https://bugs.freedesktop.org/show_bug.cgi?id=100023 is
useful here because I think it summarizes the issue quite well: 
(In reply to Michał Kopeć from comment 21)
> 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.

In accordance with https://01.org/linuxgraphics/documentation/how-report-bugs,
I can provide the information needed. As this is a 'DRM Kernel' bug, I will
provide logs from my system running the latest drm-tip branch of the kernel.

-- 
You are receiving this mail because:
You are the assignee for the bug.
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/20180809/76c19bdd/attachment.html>