Re: PCIe capture driver

2015-11-10 Thread Hans Verkuil
On 11/11/2015 07:04 AM, Ran Shalit wrote: > On Wed, Oct 28, 2015 at 12:50 AM, Hans Verkuil wrote: >> >> >> On 10/27/2015 22:56, Ran Shalit wrote: >>> On Tue, Oct 27, 2015 at 12:21 AM, Hans Verkuil wrote: On 10/27/2015 02:04, Ran Shalit wrote: > On Mon, Oct 26, 2015 at 1:46 PM,

Re: PCIe capture driver

2015-11-10 Thread Ran Shalit
On Wed, Oct 28, 2015 at 12:50 AM, Hans Verkuil wrote: > > > On 10/27/2015 22:56, Ran Shalit wrote: >> On Tue, Oct 27, 2015 at 12:21 AM, Hans Verkuil wrote: >>> >>> >>> On 10/27/2015 02:04, Ran Shalit wrote: On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth wrote: >> No, use V4L2. What you do

Re: PCIe capture driver

2015-10-30 Thread Ran Shalit
On Wed, Oct 28, 2015 at 12:50 AM, Hans Verkuil wrote: > > > On 10/27/2015 22:56, Ran Shalit wrote: >> On Tue, Oct 27, 2015 at 12:21 AM, Hans Verkuil wrote: >>> >>> >>> On 10/27/2015 02:04, Ran Shalit wrote: On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth wrote: >> No, use V4L2. What you do

Re: PCIe capture driver

2015-10-27 Thread Hans Verkuil
On 10/27/2015 22:56, Ran Shalit wrote: > On Tue, Oct 27, 2015 at 12:21 AM, Hans Verkuil wrote: >> >> >> On 10/27/2015 02:04, Ran Shalit wrote: >>> On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth wrote: > No, use V4L2. What you do with the frame after it has been captured > into memory has

Re: PCIe capture driver

2015-10-27 Thread Ran Shalit
On Tue, Oct 27, 2015 at 12:21 AM, Hans Verkuil wrote: > > > On 10/27/2015 02:04, Ran Shalit wrote: >> On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth 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 m

Re: PCIe capture driver

2015-10-26 Thread Hans Verkuil
On 10/27/2015 02:04, Ran Shalit wrote: > On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth 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

Re: PCIe capture driver

2015-10-26 Thread Steven Toth
>> Hans is absolutely correct, don't make the mistake of going >> proprietary with your API. Take advantage of the massive amount of > 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 >

Re: PCIe capture driver

2015-10-26 Thread Jean-Michel Hautbois
Hi Ran, 2015-10-26 18:04 GMT+01:00 Ran Shalit : > On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth 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 sour

Re: PCIe capture driver

2015-10-26 Thread Ran Shalit
On Mon, Oct 26, 2015 at 1:46 PM, Steven Toth 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 sp

Re: PCIe capture driver

2015-10-26 Thread Steven Toth
> 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

Re: PCIe capture driver

2015-10-25 Thread Hans Verkuil
On 10/25/2015 21:16, Ran Shalit wrote: > On Sat, Oct 24, 2015 at 11:38 AM, Hans Verkuil wrote: >> >> >> On 10/23/2015 23:57, Ran Shalit wrote: >>> On Tue, Oct 20, 2015 at 9:23 AM, Hans Verkuil wrote: On 10/19/2015 10:26 PM, Ran Shalit wrote: > Hello, > > When writing a device d

Re: PCIe capture driver

2015-10-25 Thread Ran Shalit
On Sat, Oct 24, 2015 at 11:38 AM, Hans Verkuil wrote: > > > On 10/23/2015 23:57, Ran Shalit wrote: >> On Tue, Oct 20, 2015 at 9:23 AM, Hans Verkuil wrote: >>> On 10/19/2015 10:26 PM, Ran Shalit wrote: Hello, When writing a device driver for capturing video coming from PCIe, d

Re: PCIe capture driver

2015-10-24 Thread Hans Verkuil
On 10/23/2015 23:57, Ran Shalit wrote: > On Tue, Oct 20, 2015 at 9:23 AM, Hans Verkuil 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) , ? >> >>

Re: PCIe capture driver

2015-10-23 Thread Ran Shalit
On Tue, Oct 20, 2015 at 9:23 AM, Hans Verkuil 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 t

Re: PCIe capture driver

2015-10-19 Thread Ran Shalit
On Tue, Oct 20, 2015 at 9:23 AM, Hans Verkuil 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 t

Re: PCIe capture driver

2015-10-19 Thread Hans Verkuil
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 yo

PCIe capture driver

2015-10-19 Thread Ran Shalit
Hello, When writing a device driver for capturing video coming from PCIe, does it need to be used as v4l device (video for linux) , ? Regards, Ran -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info a