[Bug 46800] [SNB] Full/Limited Color range not functional
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Jan 14 06:32:32 PST 2013
https://bugs.freedesktop.org/show_bug.cgi?id=46800
Ville Syrjala <ville.syrjala at linux.intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|daniel at ffwll.ch |ville.syrjala at linux.intel.c
| |om
--- Comment #9 from Ville Syrjala <ville.syrjala at linux.intel.com> ---
(In reply to comment #8)
> The CEA mode and DVI solution sounds promising and probably (largely?)
> explains what we see with drivers from nvidia or under windows (which
> afaik default to limited range on televisions, full range on
> monitors). As for how to treat automation, my personal preference
> would be automatic but with manual override - how this would impact
> existing users is of course the clincher. I also tend to think that
> the selection should move to the xorg.conf rather than require xrandr.
I just posted the first cut for an automatic solution to the mailing list.
It's also available in my git tree here:
https://gitorious.org/vsyrjala/linux/commits/rgb_quant_range2
I wasn't able to test the AVI infoframe stuff as my TV doesn't support it. But
otherwise it seems to work as intended, ie. the driver changes to limited range
when a CEA video mode (except 640x480) is used, and otherwise uses full range.
My TV seems fairly happy with it, assuming I haven't changed the defaults on
the TV side. This TV allows me to select the quantization range in CEA modes,
and it remembers the selection for each mode. The default I assume is limited
range for those. For non-CEA modes the TV is hardcoded to use full range,
without any option to override it.
As for xorg.conf, I'll leave stuff like that for Chris to decide.
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130114/1f152fe7/attachment.html>
More information about the intel-gfx-bugs
mailing list