From: Hans Verkuil <hverkuil@xs4all.nl>
To: Ran Shalit <ranshalit@gmail.com>, linux-media@vger.kernel.org
Subject: Re: videobuf & read/write operation
Date: Sun, 01 Nov 2015 20:39:44 +0100 [thread overview]
Message-ID: <56366A80.5090001@xs4all.nl> (raw)
In-Reply-To: <CAJ2oMhJOu8Ltra-bbb6FW3gLrCab1yKKu_zdSTNmqT5ecMkELQ@mail.gmail.com>
On 11/01/2015 08:21 PM, Ran Shalit wrote:
> Hello,
>
> I'm trying to understand how to imeplement v4l driver using videobuf.
> The videobuf documentation if very helpful.
Don't use videobuf! Use videobuf2, just like the skeleton driver.
The old videobuf framework is deprecated and you shouldn't use it as it is
horrible.
Why on earth are you trying to use videobuf if the skeleton driver clearly
uses vb2?
Regards,
Hans
> When the documentation refers to " I/O stream" , does it also include
> the read/write operation or only streaming I/O method ?
>
> In case I am using only read/write, do I need to implement all these 4 APIs:
>
> struct videobuf_queue_ops {
> int (*buf_setup)(struct videobuf_queue *q,
> unsigned int *count, unsigned int *size);
> int (*buf_prepare)(struct videobuf_queue *q,
> struct videobuf_buffer *vb,
> enum v4l2_field field);
> void (*buf_queue)(struct videobuf_queue *q,
> struct videobuf_buffer *vb);
> void (*buf_release)(struct videobuf_queue *q,
> struct videobuf_buffer *vb);
> };
>
> Are these APIs relevant for both read/write and streaminf I/O ?
>
> Best Regards,
> Ran
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-11-01 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 19:21 videobuf & read/write operation Ran Shalit
2015-11-01 19:39 ` Hans Verkuil [this message]
2015-11-01 20:13 ` Ran Shalit
2015-11-01 21:48 ` Hans Verkuil
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=56366A80.5090001@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=ranshalit@gmail.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