On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth <stoth@xxxxxxxxxxxxxx> wrote: >> No, use V4L2. What you do with the frame after it has been captured >> into memory has no relevance to the API you use to capture into memory. > > Ran, I've built many open and closed source Linux drivers over the > last 10 years - so I can speak with authority on this. > > Hans is absolutely correct, don't make the mistake of going > proprietary with your API. Take advantage of the massive amount of > video related frameworks the kernel has to offer. It will get you to > market faster, assuming your goal is to build a driver that is open > source. If your licensing prohibits an open source driver solution, > you'll have no choice but to build your own proprietary API. > > -- > Steven Toth - Kernel Labs > http://www.kernellabs.com Hi, Thank you very much for these valuable comments. If I may ask one more on this issue: Is there an example in linux tree, for a pci device which is used both as a capture and a display device ? (I've made a search but did not find any) The PCIe device we are using will be both a capture device and output video device (for display). Many Thanks, Ran -- 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
