[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

Nicholas Stommel (nicholas.stommel at gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nicholas.stommel at gmail.com

--- Comment #14 from Nicholas Stommel (nicholas.stommel at gmail.com) ---
HDMI I can understand why the default output range is 16:235 RGB, as that
conforms directly to the old HDMI spec. However, the fact that full-range RGB
is not correctly used over DisplayPort is absolutely nonsensical. No monitors
that use DisplayPort expect to receive a limited 16:235 RGB picture. A more apt
example is that 16:235 is used exclusively for televisions which do not and
never will use DisplayPort. After questioning why everything looked so
washed-out on my Linux installation, I discovered the xrandr --output DP-1
--set "Broadcast RGB" "Full" command.

However, with the introduction of Wayland and further unwillingness of
developers to add color range settings to individual compositors (which is
appropriate given such a demand is frankly a massive mistake on the Wayland
developers' end), it eventually comes down to literally needing to fish through
the i915 module and recompile the kernel completely using a variant of Tom
Yan's patch to receive a normal picture. Aside from somewhat caustic remarks by
Tom, the issue still stands and his point remains valid over three years later.

For some arcane reason, HDMI output from my i7-7700 HD 630 graphics actually
does default to sending full-range color to my monitor. There doesn't really
appear to be much rhyme or reason for "following the Intel spec" that clearly
doesn't follow decade-long established DisplayPort standards. Dmitry is correct
here, this really is horrible from a user point of view.

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