From: Hans Verkuil <hverkuil@xs4all.nl>
To: Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: [PATCH] libv4lconvert: add support for new pixelformats
Date: Fri, 18 Jul 2014 00:27:42 +0200 [thread overview]
Message-ID: <53C84DDE.4000701@xs4all.nl> (raw)
Support for alpha-channel aware pixelformats was added. Recognize those formats
in libv4lconvert.
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
diff --git a/lib/libv4lconvert/libv4lconvert.c b/lib/libv4lconvert/libv4lconvert.c
index 7ee7c19..cea65aa 100644
--- a/lib/libv4lconvert/libv4lconvert.c
+++ b/lib/libv4lconvert/libv4lconvert.c
@@ -86,6 +86,10 @@ static const struct v4lconvert_pixfmt supported_src_pixfmts[] = {
{ V4L2_PIX_FMT_RGB565, 16, 4, 6, 0 },
{ V4L2_PIX_FMT_BGR32, 32, 4, 6, 0 },
{ V4L2_PIX_FMT_RGB32, 32, 4, 6, 0 },
+ { V4L2_PIX_FMT_XBGR32, 32, 4, 6, 0 },
+ { V4L2_PIX_FMT_XRGB32, 32, 4, 6, 0 },
+ { V4L2_PIX_FMT_ABGR32, 32, 4, 6, 0 },
+ { V4L2_PIX_FMT_ARGB32, 32, 4, 6, 0 },
/* yuv 4:2:2 formats */
{ V4L2_PIX_FMT_YUYV, 16, 5, 4, 0 },
{ V4L2_PIX_FMT_YVYU, 16, 5, 4, 0 },
@@ -1121,6 +1125,8 @@ static int v4lconvert_convert_pixfmt(struct v4lconvert_data *data,
break;
case V4L2_PIX_FMT_RGB32:
+ case V4L2_PIX_FMT_XRGB32:
+ case V4L2_PIX_FMT_ARGB32:
if (src_size < (width * height * 4)) {
V4LCONVERT_ERR("short rgb32 data frame\n");
errno = EPIPE;
@@ -1143,6 +1149,8 @@ static int v4lconvert_convert_pixfmt(struct v4lconvert_data *data,
break;
case V4L2_PIX_FMT_BGR32:
+ case V4L2_PIX_FMT_XBGR32:
+ case V4L2_PIX_FMT_ABGR32:
if (src_size < (width * height * 4)) {
V4LCONVERT_ERR("short bgr32 data frame\n");
errno = EPIPE;
next reply other threads:[~2014-07-17 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 22:27 Hans Verkuil [this message]
2014-07-18 10:01 ` [PATCH] libv4lconvert: add support for new pixelformats Hans de Goede
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=53C84DDE.4000701@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.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.