From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: dri-devel@lists.freedesktop.org, Rob Clark <robdclark@gmail.com>,
Dave Airlie <airlied@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 16/28] drm/i2c: tda998x: change the video quantization
Date: Sat, 11 Jan 2014 18:22:57 +0000 [thread overview]
Message-ID: <20140111182257.GE15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140109120500.6abc6cd2@armhf>
On Thu, Jan 09, 2014 at 12:05:00PM +0100, Jean-Francois Moine wrote:
> This patch changes the video quantization to RGB/YUV.
Strong NAK, this patch is definitely incorrect.
The Cubox (which I assume is the platform you're generating these patches
for) produces RGB at it's output, which are the RGB values from the
framebuffer. Being a computer-like "IT" source, these RGB values have the
full range, from zero to 255, rather than the limited range of 16 to 235.
With limited range, a value of 16 is black and 235 is white. However, the
values in the framebuffer will be zero for black and 255 for white.
A VQR value of 1 gives limited range of 16 to 235, whereas zero gives
full range. The value of zero is correct here.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
prev parent reply other threads:[~2014-01-11 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 11:05 [PATCH v2 16/28] drm/i2c: tda998x: change the video quantization Jean-Francois Moine
2014-01-11 18:22 ` Russell King - ARM Linux [this message]
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=20140111182257.GE15937@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=robdclark@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox