From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm: add an fb creation ioctl that takes a pixel format v4
Date: Tue, 15 Nov 2011 08:16:04 -0800 [thread overview]
Message-ID: <20111115081604.2e3b6dfa@jbarnes-desktop> (raw)
In-Reply-To: <20111115125702.GL3477@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1294 bytes --]
On Tue, 15 Nov 2011 14:57:02 +0200
Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> I'm fine with fourccs as long as the defines are named and documented
> in way that avoids guesswork.
>
> So what I'm thinking is something like this:
>
> DRM_FOURCC_RGB332 ... /* [7:0] R:G:B 3:3:2 */
> DRM_FOURCC_XRGB1555 ... /* [15:0] x:R:G:B 1:5:5:5, native endian */
> DRM_FOURCC_RGB565 ... /* [15:0] R:G:B 5:6:5, native endian */
> DRM_FOURCC_XRGB8888 ... /* [31:0] x:R:G:B 8:8:8:8, native endian */
> DRM_FOURCC_XRGB2101010 ... /* [31:0] x:R:G:B 2:10:10:10, native endian */
>
> DRM_FOURCC_RGB888 ... /* [23:0] R:G:B 8:8:8, little endian */
> DRM_FOURCC_BGR888 ... /* [23:0] B:G:R 8:8:8, little endian */
>
> DRM_FOURCC_YUYV ... /* [31:0] Cr:Y1:Cb:Y0 8:8:8:8, little endian */
> DRM_FOURCC_UYVY ... /* [31:0] Y1:Cr:Y0:Cb 8:8:8:8, little endian */
> DRM_FOURCC_YVYU ... /* [31:0] Cb:Y1:Cr:Y0 8:8:8:8, little endian */
> DRM_FOURCC_VYUY ... /* [31:0] Y1:Cb:Y0:Cr 8:8:8:8, little endian */
>
> That leaves no room for guesswork.
Looks great. Want to send Dave an incremental patch? I'll apply the
final version to libdrm for use by userland code.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-11-15 16:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 20:21 [PATCH 1/2] drm: add plane support v2 Jesse Barnes
2011-11-14 20:21 ` [PATCH 2/2] drm: add an fb creation ioctl that takes a pixel format v4 Jesse Barnes
2011-11-14 21:16 ` Ville Syrjälä
2011-11-14 21:22 ` Jesse Barnes
2011-11-15 12:57 ` Ville Syrjälä
2011-11-15 16:16 ` Jesse Barnes [this message]
2011-11-15 20:30 ` Ville Syrjälä
2011-11-15 20:55 ` Jesse Barnes
2011-11-14 21:36 ` Rob Clark
2011-11-14 21:24 ` Ville Syrjälä
2011-11-14 21:35 ` Jesse Barnes
2011-11-14 22:37 ` Ville Syrjälä
2011-11-14 22:53 ` Jesse Barnes
2011-11-15 2:40 ` [PATCH 1/2] drm: add plane support v2 Ben Skeggs
2011-11-15 11:42 ` Ville Syrjälä
2011-11-15 16:13 ` Jesse Barnes
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=20111115081604.2e3b6dfa@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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