From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Keith Packard <keithp@keithp.com>
Cc: "Kristian Høgsberg" <hoegsberg@gmail.com>,
"Linux Fbdev development list" <linux-fbdev@vger.kernel.org>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
"Mesa Dev" <mesa-dev@lists.freedesktop.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [Intel-gfx] [Mesa-dev] [PATCH] dri3, i915, i965: Add __DRI_IMAGE_FOURCC_SARGB8888
Date: Sat, 23 Nov 2013 01:10:37 +0000 [thread overview]
Message-ID: <20131123011037.GO10036@intel.com> (raw)
In-Reply-To: <86pppsvw8e.fsf@miki.keithp.com>
On Fri, Nov 22, 2013 at 03:43:13PM -0800, Keith Packard wrote:
> Ville Syrjälä <ville.syrjala@linux.intel.com> writes:
>
> > What is this format anyway? -ENODOCS
>
> Same as MESA_FORMAT_SARGB8 and __DRI_IMAGE_FORMAT_SARGB8 :-)
>
> > If its just an srgb version of ARGB8888, then I wouldn't really want it
> > in drm_fourcc.h. I expect colorspacy stuff will be handled by various
> > crtc/plane properties in the kernel so we don't need to encode that
> > stuff into the fb format.
>
> It's not any different from splitting YUV codes from RGB codes;
Not really. Saying something is YUV (or rather Y'CbCr) doesn't
actually tell you the color space. It just tells you whether the
information is encoded as R+G+B or Y+Cb+Cr. How you convert between
them is another matter. You need to know the gamma, color primaries,
chroma siting for sub-sampled YCbCr formats, etc.
--
Ville Syrjälä
Intel OTC
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Keith Packard <keithp@keithp.com>
Cc: "Kristian Høgsberg" <hoegsberg@gmail.com>,
"Linux Fbdev development list" <linux-fbdev@vger.kernel.org>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
"Mesa Dev" <mesa-dev@lists.freedesktop.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [Intel-gfx] [Mesa-dev] [PATCH] dri3, i915, i965: Add __DRI_IMAGE_FOURCC_SARGB8888
Date: Sat, 23 Nov 2013 03:10:37 +0200 [thread overview]
Message-ID: <20131123011037.GO10036@intel.com> (raw)
In-Reply-To: <86pppsvw8e.fsf@miki.keithp.com>
On Fri, Nov 22, 2013 at 03:43:13PM -0800, Keith Packard wrote:
> Ville Syrjälä <ville.syrjala@linux.intel.com> writes:
>
> > What is this format anyway? -ENODOCS
>
> Same as MESA_FORMAT_SARGB8 and __DRI_IMAGE_FORMAT_SARGB8 :-)
>
> > If its just an srgb version of ARGB8888, then I wouldn't really want it
> > in drm_fourcc.h. I expect colorspacy stuff will be handled by various
> > crtc/plane properties in the kernel so we don't need to encode that
> > stuff into the fb format.
>
> It's not any different from splitting YUV codes from RGB codes;
Not really. Saying something is YUV (or rather Y'CbCr) doesn't
actually tell you the color space. It just tells you whether the
information is encoded as R+G+B or Y+Cb+Cr. How you convert between
them is another matter. You need to know the gamma, color primaries,
chroma siting for sub-sampled YCbCr formats, etc.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-11-23 1:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 4:12 [PATCH] dri3, i915, i965: Add __DRI_IMAGE_FOURCC_SARGB8888 Keith Packard
2013-11-22 10:26 ` Daniel Vetter
2013-11-22 11:01 ` [Mesa-dev] " Keith Packard
2013-11-22 16:17 ` Daniel Vetter
2013-11-22 16:17 ` Daniel Vetter
2013-11-22 16:17 ` Daniel Vetter
2013-11-22 17:46 ` Ville Syrjälä
2013-11-22 17:46 ` Ville Syrjälä
2013-11-22 22:12 ` [Intel-gfx] " Kristian Høgsberg
2013-11-22 22:12 ` Kristian Høgsberg
2013-11-22 23:05 ` Ville Syrjälä
2013-11-22 23:05 ` Ville Syrjälä
2013-11-22 23:43 ` Keith Packard
2013-11-22 23:43 ` Keith Packard
2013-11-22 23:43 ` Keith Packard
2013-11-23 1:10 ` Ville Syrjälä [this message]
2013-11-23 1:10 ` Ville Syrjälä
2013-11-25 14:57 ` Geert Uytterhoeven
2013-11-25 14:57 ` Geert Uytterhoeven
2013-11-25 14:57 ` Geert Uytterhoeven
2013-11-22 23:36 ` [Intel-gfx] " Keith Packard
2013-11-22 23:36 ` Keith Packard
2013-11-22 23:36 ` [Intel-gfx] " Keith Packard
2013-11-25 8:57 ` [Intel-gfx] [Mesa-dev] " Daniel Vetter
2013-11-25 8:57 ` Daniel Vetter
2013-11-25 8:57 ` Daniel Vetter
2013-11-25 14:15 ` [Intel-gfx] " Ville Syrjälä
2013-11-25 14:15 ` Ville Syrjälä
2013-11-25 14:15 ` Ville Syrjälä
[not found] ` <16967_1385369810_529310D2_16967_15891_1_20131125085723.GW27344@phenom.ffwll.local>
2013-11-25 15:14 ` i830 watermark problems - status? Thomas Richter
2013-11-25 15:23 ` Daniel Vetter
[not found] ` <26487_1385392973_52936B4D_26487_126_1_20131125152331.GB27344@phenom.ffwll.local>
2013-11-25 15:55 ` Thomas Richter
2013-11-25 20:30 ` Daniel Vetter
[not found] ` <26487_1385411456_5293B380_26487_2367_1_CAKMK7uFFZcf92XbzA9Mj2c0fdhDWZMKkZVNK9yy8Shc8pcLygg@mail.gmail.com>
2013-11-30 20:11 ` Thomas Richter
2013-12-19 14:01 ` intel-drm-nightly: hang and black screen on i830 Thomas Richter
2013-11-25 22:08 ` [PATCH] dri3, i915, i965: Add __DRI_IMAGE_FOURCC_SARGB8888 Eric Anholt
2013-12-13 22:58 ` Kenneth Graunke
2013-12-14 0:37 ` [Mesa-dev] " Keith Packard
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=20131123011037.GO10036@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hoegsberg@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mesa-dev@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.