[Bug 55121] Limited color range on screen that is connected via HDMI [SandyBridge]
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Thu Apr 11 02:11:54 PDT 2013
https://bugzilla.kernel.org/show_bug.cgi?id=55121
--- Comment #9 from Daniel Vetter <daniel at ffwll.ch> 2013-04-11 09:11:54 ---
On Thu, Apr 11, 2013 at 11:00 AM, <bugzilla-daemon at bugzilla.kernel.org> wrote:
>> I was just trying to figure out how can we emerge from this, if specs werent
>> followed strictly - problems are bound to happen either way and the only thing
>> that can help the end user is to set the parameters himself. Personally I'm
>> wondering is there a way and how ?
>
> The only chance I see is that we'd detect somehow that the display is using
> full range by default. I was thinking that it might be a more general issue
> with monitors, whereas TVs would be more likely to use limited range. But
> unfortunately I don't know of any way to tell TVs and monitors apart based on
> the EDID information. A blacklist would be another option, but that approach
> won't scale very well.
At least my 24" desktop screens from HP here implement the
limited/full color range stuff according to spec on HDMI. So I don't
think it's an issue with TV vs. computer screens, but probably more
with sloppy/cheap vs. not-so-cheap ...
I think this is not a game we can't win, but with the automatic mode
we should at least make conformant hw work. Anything else needs manual
configuration anyway :(
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the intel-gfx-bugs
mailing list