From: Joakim Plate <elupus@ecce.se>
To: dri-devel@lists.freedesktop.org
Subject: Re: [i915] Backlight brighter since 3.9.0
Date: Wed, 22 May 2013 16:08:38 +0000 (UTC) [thread overview]
Message-ID: <loom.20130522T180548-644@post.gmane.org> (raw)
In-Reply-To: CAO_aot7kZWzxudz8CX_FS4Hznk0foPcDz1xevZP=e-og0tjF5w@mail.gmail.com
Hi,
>
> 2013/5/20 Daniel Vetter <daniel <at> ffwll.ch>
> Yeah, this is a feature. HDMI has (for oddball backwards compat with
> analog TV signals) a special mode which reduces the useable RGB value
> range by chopping off about 10% at the bottom and top end. This results in
> light colors getting brighter and dark colors getting darker.
> The above mentioned commit tries (to the best of our knowledge) to
> auto-set the option which most likely fits what the hdmi sink will do with
> the color data. You can either fix this up in the hdmi sink with the
> on-screen menu or by manually setting the "RBG Broadcast" property for the
> relevant hdmi connector to the setting you want.
> Cheers, Daniel--
> Daniel Vetter
> Software Engineer, Intel Corporation+41 (0) 79 365 57 48 -
http://blog.ffwll.ch
>
Does this mean the system is doing RGB full range to limited range
compression on the raw RGB data it receives from an application?
Ie a video player that want to be able to handle blacker than black
properly will need to force the GPU into fullrange output to avoid
the driver internal compression of the signal and handle that itself?
/Joakim
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-05-22 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 22:39 [i915] Backlight brighter since 3.9.0 Jan Hinnerk Stosch
2013-05-20 21:55 ` Daniel Vetter
2013-05-21 6:29 ` Jan Hinnerk Stosch
2013-05-22 16:08 ` Joakim Plate [this message]
2013-05-22 16:56 ` Daniel Vetter
2013-06-03 16:13 ` Aaron Plattner
2013-06-03 19:36 ` Daniel Vetter
2013-06-03 19:42 ` Aaron Plattner
2013-06-03 20:03 ` Daniel Vetter
2013-06-03 21:10 ` Alex Deucher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20130522T180548-644@post.gmane.org \
--to=elupus@ecce.se \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.