From: Hans Verkuil <hverkuil@xs4all.nl>
To: Ran Shalit <ranshalit@gmail.com>, linux-media@vger.kernel.org
Subject: Re: PCIe capture driver
Date: Tue, 20 Oct 2015 08:23:06 +0200 [thread overview]
Message-ID: <5625DDCA.2040203@xs4all.nl> (raw)
In-Reply-To: <CAJ2oMhJinTjko5N+JdCYrenxme7xUJ_LudwtUy4TJMi1RD6Xag@mail.gmail.com>
On 10/19/2015 10:26 PM, Ran Shalit wrote:
> Hello,
>
> When writing a device driver for capturing video coming from PCIe,
> does it need to be used as v4l device (video for linux) , ?
Yes. If you don't then 1) you will never be able to upstream the driver,
2) any application that wants to use your driver will need custom code to
talk to your driver, 3) it will be a lot more work to write the driver
since you can't use the V4L2 kernel frameworks it provides or ask for
help.
Basically, by deciding to reinvent the wheel you're screwing over your
customers and yourself.
Here is a nice PCI(e) template driver that you can use as your starting
point: Documentation/video4linux/v4l2-pci-skeleton.c
Regards,
Hans
next prev parent reply other threads:[~2015-10-20 6:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 20:26 PCIe capture driver Ran Shalit
2015-10-20 6:23 ` Hans Verkuil [this message]
2015-10-20 6:38 ` Ran Shalit
2015-10-23 21:57 ` Ran Shalit
2015-10-24 9:38 ` Hans Verkuil
2015-10-25 20:16 ` Ran Shalit
2015-10-25 22:55 ` Hans Verkuil
2015-10-26 11:46 ` Steven Toth
2015-10-26 17:04 ` Ran Shalit
2015-10-26 17:10 ` Jean-Michel Hautbois
2015-10-26 17:22 ` Steven Toth
2015-10-26 22:21 ` Hans Verkuil
2015-10-27 13:56 ` Ran Shalit
2015-10-27 22:50 ` Hans Verkuil
2015-10-30 9:18 ` Ran Shalit
2015-11-11 6:04 ` Ran Shalit
2015-11-11 7:22 ` 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=5625DDCA.2040203@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;
as well as URLs for NNTP newsgroup(s).