From: Wu-Cheng Li <wuchengli@chromium.org>
To: mchehab@osg.samsung.com, hverkuil@xs4all.nl, crope@iki.fi,
ricardo.ribalda@gmail.com, p.zabel@pengutronix.de,
wuchengli@chromium.org, shuahkh@osg.samsung.com,
hans.verkuil@cisco.com, renesas@ideasonboard.com,
guennadi.liakhovetski@intel.com, sakari.ailus@linux.intel.com,
posciak@chromium.org, djkurtz@chromium.org,
tiffany.lin@mediatek.com, pc.chen@mediatek.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 1/3] videodev2.h: add V4L2_PIX_FMT_VP9 format.
Date: Tue, 24 May 2016 23:05:21 +0800 [thread overview]
Message-ID: <1464102324-53965-2-git-send-email-wuchengli@chromium.org> (raw)
In-Reply-To: <1464102324-53965-1-git-send-email-wuchengli@chromium.org>
This adds VP9 video coding format, a successor to VP8.
Signed-off-by: Wu-Cheng Li <wuchengli@chromium.org>
---
include/uapi/linux/videodev2.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
index 8f95191..a95f940 100644
--- a/include/uapi/linux/videodev2.h
+++ b/include/uapi/linux/videodev2.h
@@ -594,6 +594,7 @@ struct v4l2_pix_format {
#define V4L2_PIX_FMT_VC1_ANNEX_G v4l2_fourcc('V', 'C', '1', 'G') /* SMPTE 421M Annex G compliant stream */
#define V4L2_PIX_FMT_VC1_ANNEX_L v4l2_fourcc('V', 'C', '1', 'L') /* SMPTE 421M Annex L compliant stream */
#define V4L2_PIX_FMT_VP8 v4l2_fourcc('V', 'P', '8', '0') /* VP8 */
+#define V4L2_PIX_FMT_VP9 v4l2_fourcc('V', 'P', '9', '0') /* VP9 */
/* Vendor-specific formats */
#define V4L2_PIX_FMT_CPIA1 v4l2_fourcc('C', 'P', 'I', 'A') /* cpia1 YUV */
--
2.8.0.rc3.226.g39d4020
next prev parent reply other threads:[~2016-05-24 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 15:05 [PATCH v1 0/3] Add V4L2_PIX_FMT_VP9 Wu-Cheng Li
2016-05-24 15:05 ` Wu-Cheng Li [this message]
2016-05-24 15:05 ` [PATCH v1 2/3] v4l2-ioctl: add VP9 format description Wu-Cheng Li
2016-05-24 15:05 ` [PATCH v1 3/3] V4L: add VP9 format documentation Wu-Cheng Li
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=1464102324-53965-2-git-send-email-wuchengli@chromium.org \
--to=wuchengli@chromium.org \
--cc=crope@iki.fi \
--cc=djkurtz@chromium.org \
--cc=guennadi.liakhovetski@intel.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=p.zabel@pengutronix.de \
--cc=pc.chen@mediatek.com \
--cc=posciak@chromium.org \
--cc=renesas@ideasonboard.com \
--cc=ricardo.ribalda@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=shuahkh@osg.samsung.com \
--cc=tiffany.lin@mediatek.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;
as well as URLs for NNTP newsgroup(s).