From: Lamarque Vieira Souza <lamarque@gmail.com>
To: video4linux-list@redhat.com
Subject: Re: how to make qbuf
Date: Wed, 8 Jul 2009 12:57:01 -0300 [thread overview]
Message-ID: <200907081257.02308.lamarque@gmail.com> (raw)
In-Reply-To: <3a9b62b20907062344p56d1ecafsbbb936c74eadfd43@mail.gmail.com>
Em Tuesday 07 July 2009, 서정민 escreveu:
> Hi.
Hi,
> I'm making V4l2 device driver for mplayer.
mplayer already implements v4l2 specification, you do not need to implement a
driver for it.
> But
> It's too difficult to understand V4l2 driver internal structure.
>
> I can't understand how to use VIDIOC_QBUF, VIDIOC_DQBUF ioctl and 'struct
> videobuf_queue'
VIDIOC_QBUF queues a buffer (struct v4l2_buffer) to a buffer list managed by
the device driver (usually a kernel module). The driver fills the buffer with
needed information (image data, compression type, etc) and the application
must use VIDIOC_DQBUF to get the filled buffer from the device driver's buffer
list. Applications, such as mplayer must use VIDIOC_QBUF and VIDIOC_DQBUF.
videobuf_queue is used by the device driver (kernel space) to manage the
buffer list. If you are creating/changing an application (mplayer) you do not
need to know about videobuf_queue. If you are creating a device driver for a
capture device (webcam, etc) in kernel space then using videobuf_queue will
make your life easier.
> Why does v4l2 driver need to use 'videobuf_queue'?
videobuf_queue is not mandatory but it will make it easier to manage video
frames and implement some needed ioctls in the device driver.
> Please. tell me v4l2 driver internal operation.
You can read more bout v4l2 here http://v4l2spec.bytesex.org/spec-
single/v4l2.html
> Thanks.
> --
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
--
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
--
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:[~2009-07-08 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 6:44 how to make qbuf 서정민
2009-07-07 13:23 ` Rafael Diniz
2009-07-08 15:57 ` Lamarque Vieira Souza [this message]
2009-07-09 2:53 ` Dongsoo, Nathaniel Kim
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=200907081257.02308.lamarque@gmail.com \
--to=lamarque@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.