On 10/23/2015 23:57, Ran Shalit wrote: > On Tue, Oct 20, 2015 at 9:23 AM, Hans Verkuil <hverkuil@xxxxxxxxx> wrote: >> 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 > > Hi Hans, > > I now understand, that I will be using media sdk (Intel) which is > based on DRM framework, and does not use v4l. DRM is for video output, not video capture. So this seems irrelevant. > So I probably need to do some custom driver for delivering video with PCIe. There is only one linux API for video capture: V4L2. What PCIe card are we talking about here? What are you trying to achieve? Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
