From: Hans Verkuil <hansverk@cisco.com>
To: linux-media <linux-media@vger.kernel.org>
Subject: RFC: V4L2_PIX_FMT_NV16: should it allow padding after each plane?
Date: Wed, 31 Aug 2016 10:43:03 +0200 [thread overview]
Message-ID: <57C69897.8010200@cisco.com> (raw)
The NV16 documentation allows for padding after each line:
https://hverkuil.home.xs4all.nl/spec/uapi/v4l/pixfmt-nv16.html
But I have one case where there is also padding after each plane.
Can we fold that into the existing NV16 format? I.e., in that case
the size of each plane is sizeimage / 2.
Or do I have to make a new NV16PAD format that allows such padding?
I am in favor of extending the NV16 specification since I believe it
makes sense, but I want to know what others think.
Regards,
Hans
next reply other threads:[~2016-08-31 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 8:43 Hans Verkuil [this message]
2016-08-31 12:57 ` RFC: V4L2_PIX_FMT_NV16: should it allow padding after each plane? Sakari Ailus
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=57C69897.8010200@cisco.com \
--to=hansverk@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox