Bug 87591

Summary: Additional Color Space/Pixel Map Formats for HDMI
Product: xorg Reporter: Pitscho <friedrich.timo>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: enhancement    
Priority: medium CC: friedrich.timo, fritsch, lee295012, rob
Version: unspecified   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Pitscho 2014-12-22 13:07:36 UTC 
The OSS driver only supports Full RGB. In case of home theater setups (e.g. XBMC) and an AV-Receiver, this has several drawbacks. E.g. the google chromecast only supports limited RGB/YCbCr, but the TV screen is only connected to the AV-Receiver. So if one changes the input at the AV-Receiver side, the color spaces of the sources and the screen might match or don't.

An option, like it is available at the AMDs fglrx side (full RGB, limited Studio RGB, YCbCr 4:4:, YCbCr 4:2:2) would be a big improvement ot the OSS radeon driver, especially for all HTPC users.

Even though on can argue to simply change all devices to full RGB, this might not even be possible. As mentioned the chromecast has no setting to change this. Furthermore the TV/Blueray/DVD ... devices are more focused on the YCbCr format, which in some cases produces better picture quality.
Comment 1 Pitscho 2015-02-26 11:41:00 UTC 
Any update of this topic?

Plans?

How does e.g. openElec face this problem? Theses tiny machines are often also connected to an AV-Receiver, so a native YCbCr support would be beneficial there too.
Comment 2 Alex Deucher 2015-02-26 15:03:13 UTC 

*** This bug has been marked as a duplicate of bug 83226 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.