Message ID | CAB0OVGou38FQ60w9QTuBbJcvHF6f_2Xhrks0VCuXQC9V5O9YwA@mail.gmail.com |
---|---|
State | Accepted |
Headers | show |
2019-03-21 1:26 GMT+01:00, Carl Eugen Hoyos <ceffmpeg@gmail.com>: > 2018-11-19 18:41 GMT+01:00, Carl Eugen Hoyos <ceffmpeg@gmail.com>: >> 2018-11-19 18:21 GMT+01:00, Pablo Rubio Fernández >> <prubio@elitegrupo.com>: >> >>> It's my first time here. I want to create a patch to add >>> Z16 pixel format. >>> I have did some changes, and I want to know if I'll need >>> change any other file. >> >> Isn't attached poc sufficient? > > Patch attached that imo makes using z16 a little easier, > will push if there are no objections. Patch applied. Carl Eugen
From b33aac84ecce24cbe9125415c0c0e7732887dc5f Mon Sep 17 00:00:00 2001 From: Carl Eugen Hoyos <ceffmpeg@gmail.com> Date: Thu, 21 Mar 2019 01:24:42 +0100 Subject: [PATCH] lavd/v4l2-common: Add an entry for Z16. --- libavdevice/v4l2-common.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/libavdevice/v4l2-common.c b/libavdevice/v4l2-common.c index 2d6bfac..b5b4448 100644 --- a/libavdevice/v4l2-common.c +++ b/libavdevice/v4l2-common.c @@ -46,6 +46,9 @@ const struct fmt_map ff_fmt_conversion_table[] = { #ifdef V4L2_PIX_FMT_Y16 { AV_PIX_FMT_GRAY16LE,AV_CODEC_ID_RAWVIDEO, V4L2_PIX_FMT_Y16 }, #endif +#ifdef V4L2_PIX_FMT_Z16 + { AV_PIX_FMT_GRAY16LE,AV_CODEC_ID_RAWVIDEO, V4L2_PIX_FMT_Z16 }, +#endif { AV_PIX_FMT_NV12, AV_CODEC_ID_RAWVIDEO, V4L2_PIX_FMT_NV12 }, { AV_PIX_FMT_NONE, AV_CODEC_ID_MJPEG, V4L2_PIX_FMT_MJPEG }, { AV_PIX_FMT_NONE, AV_CODEC_ID_MJPEG, V4L2_PIX_FMT_JPEG }, -- 1.7.10.4