From: "Daniel Glöckner" <daniel-gl@gmx.net>
To: Dinesh Bhat <dbhat@linsys.ca>
Cc: Video-4l-list <video4linux-list@redhat.com>
Subject: Re: Apple quicktime v210 codec equivalent support on V4L
Date: Thu, 8 May 2008 17:37:20 +0200 [thread overview]
Message-ID: <20080508153720.GA2727@daniel.bse> (raw)
In-Reply-To: <48230D7E.9050503@linsys.ca>
On Thu, May 08, 2008 at 09:26:06AM -0500, Dinesh Bhat wrote:
> We have a card that supports v210 codec type on Mac OS X. We have our
> regular drivers (we implement frame buffers) and are interested in
> supporting v4l for this card. I was wondering if there is any direct
> support available for v210 codec. Can anyone please suggest what is the
> best way to go here if we want to support v4l?
If I understand you correctly, you want to write a V4L driver for this card.
There is currently no equivalent to v210 defined but adding support for it to
V4L is just a matter of adding
#define V4L2_PIX_FMT_V210 v4l2_fourcc('v','2','1','0') /* 20 YUV 4:2:2 */
to videodev2.h.
A description for the V4L2 API specification should be provided as well.
Conversion between different pixel formats is not supposed to be done in V4L
drivers. It should be done either on the card or in the application if needed.
If you need to reorder bits to have v210, invent a new pixel format and
advertise that one instead of v210. Drivers should not touch the frame buffer.
Only hardware and userspace do.
A userspace library is in the works to aid application writers:
http://linuxtv.org/v4lwiki/index.php/V4L2UserspaceLibrary
So your driver should expect the application to already know about v210.
Daniel
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
prev parent reply other threads:[~2008-05-08 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 14:26 Apple quicktime v210 codec equivalent support on V4L Dinesh Bhat
2008-05-08 15:37 ` Daniel Glöckner [this message]
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=20080508153720.GA2727@daniel.bse \
--to=daniel-gl@gmx.net \
--cc=dbhat@linsys.ca \
--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