From: "Daniel Glöckner" <daniel-gl@gmx.net>
To: "H. Willstrand" <h.willstrand@gmail.com>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>
Subject: Re: V4L2_PIX_FMT_RAW
Date: Thu, 21 Feb 2008 02:20:48 +0100 [thread overview]
Message-ID: <20080221012048.GA2924@daniel.bse> (raw)
In-Reply-To: <175f5a0f0802201602i52187c1fxb2e980c7e86fcca6@mail.gmail.com>
On Thu, Feb 21, 2008 at 01:02:39AM +0100, H. Willstrand wrote:
> What's the problem with having a name of the formalized data in the
> video stream? ie raw do not mean undefined.
I thought you wanted to avoid having to define V4L2_PIX_FMT_x for an
exploding number of proprietary formats that are quite similar but still
incompatible. It makes sense for formats that are used by more than one
driver.
> I don't see how separate RAW ioctl's will add value to the V4l2 API,
> it fits into the current API.
Yes, it does. Each driver having multiple raw formats just needs a
private control id to select one.
Daniel
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-02-21 1:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 19:25 V4L2_PIX_FMT_RAW Thomas Kaiser
[not found] ` <175f5a0f0802201208u4bca35afqc0291136fe2482b@mail.gmail.com>
[not found] ` <47BC8BFC.2000602@kaiser-linux.li>
[not found] ` <175f5a0f0802201232y6a1bfc53u4fe92fede3abcb34@mail.gmail.com>
[not found] ` <47BC90CA.1000707@kaiser-linux.li>
[not found] ` <175f5a0f0802201254q7dc96190k35caafe9ba7d3274@mail.gmail.com>
2008-02-20 21:11 ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-20 21:41 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-20 22:02 ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-20 21:58 ` V4L2_PIX_FMT_RAW Daniel Glöckner
2008-02-20 22:12 ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-20 22:41 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-20 23:20 ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-21 0:02 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 1:20 ` Daniel Glöckner [this message]
2008-02-21 9:10 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 12:00 ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-21 12:43 ` V4L2_PIX_FMT_RAW Daniel Glöckner
2008-02-21 12:48 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 12:43 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 18:55 ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-21 20:12 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 20:40 ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-21 21:06 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 21:29 ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-21 21:40 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-21 22:03 ` V4L2_PIX_FMT_RAW Laurent Pinchart
2008-02-21 22:22 ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-22 9:38 ` V4L2_PIX_FMT_RAW Thierry Merle
2008-02-22 12:22 ` V4L2_PIX_FMT_RAW Thomas Kaiser
2008-02-23 0:15 ` V4L2_PIX_FMT_RAW H. Willstrand
2008-02-23 19:51 ` V4L2_PIX_FMT_RAW Thierry Merle
2008-02-24 21:46 ` V4L2_PIX_FMT_RAW Laurent Pinchart
2008-02-21 21:59 ` V4L2_PIX_FMT_RAW Laurent Pinchart
2008-02-21 22:28 ` V4L2_PIX_FMT_RAW Thomas Kaiser
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=20080221012048.GA2924@daniel.bse \
--to=daniel-gl@gmx.net \
--cc=h.willstrand@gmail.com \
--cc=video4linux-list@redhat.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