[Bug 94921] Remove illogical/bogus "Automatic" mode from "Broadcast RGB" property

[bugzilla-daemon at bugzilla.kernel.org]

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

--- Comment #24 from Nicholas Stommel (nicholas.stommel at gmail.com) ---
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, and the core of the bug I
rather missed. Over native HDMI, interestingly, the i915 driver always selects
the correct color range for me, but only limited range color is ever selected
over DisplayPort. 

I understand now that the code conforms to spec, and I don't wish to argue
about that. What I don't get is why I always end up with washed-out limited RGB
when I should be getting full RGB. I seem to be experiencing the same problem
as others in this active bug report
https://bugs.freedesktop.org/show_bug.cgi?id=100023 , from which the following
comment of mine seems appropriate:

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

Michal's comment sums up exactly what is currently happening. 

(In reply to N. W. from comment # 8)
> That being said: Please just fix
> https://bugzilla.kernel.org/show_bug.cgi?id=94921 instead of closing it
> without listening to your customers and the other issue will solve itself.

I wholeheartedly agree with N.W. that something more needs to be done about
https://bugzilla.kernel.org/show_bug.cgi?id=94921

However, my experience with Intel has been similar to Tom Yan's on
https://bugzilla.kernel.org/show_bug.cgi?id=94921 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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.