[Bug 46800] [SNB] Full/Limited Color range not working automatically for 1000/1001 CEA modes

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Nov 18 10:48:04 PST 2013


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

--- Comment #22 from Daniel Vetter <daniel at ffwll.ch> ---
(In reply to comment #21)
> The quantization range signaling doesn't seem to be working on Haswell.
> 
> I am outputting from a D54250WYK NUC to Pioneer KRP-500m (via Yamaha
> RX-A1000) and seeing grey blacks with the default limited RGB range. When I
> switch to full range using xrandr, picture is fine. I assume my monitor
> supports switching RGB range automatically as my bluray player is able to
> signal it (switch player output RGB range between full and limited,
> displayed black levels do not change; I can verify that the output range
> really changes by setting input range manually in the Pioneer).
> 
> There are more people in the xbmc forum nuc thread (see for example starting
> at http://forum.xbmc.org/showthread.php?tid=176718&pid=1548847#pid1548847)
> reporting grey blacks with the default setting, so it's probably not just my
> system. Based on
> http://forum.xbmc.org/showthread.php?tid=176718&pid=1552262#pid1552262 (and
> the few comments following), same issue may be present on earlier chipsets
> too.
> 
> Unfortunately I don't have access to an HDMI analyzer. Is there any other
> way I could supply useful data?
> 
> 
> For best quality it would be nice to have full range output, but have the
> ability to signal limited range if desired. This would preserve
> blacker-than-black, whiter-than-white and avoid banding from luma range
> expansion.

Please file a new bug and provid details about your kernel (booting with
drm.debug=0xe and dmesg preferred, it's all in there).

-- 
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/20131118/0e9ec0f5/attachment.html>


More information about the intel-gfx-bugs mailing list