RE: Mem2Mem V4L2 devices [RFC] - Can we enhance the V4L2 API?

2009-10-08 Thread Marek Szyprowski
Hello, On Wednesday, October 07, 2009 3:39 PM Karicheri, Muralidharan wrote: As we have seen in the discussion, this is not a streaming device, rather a transaction/conversion device which operate on a given frame to get a desired output frame. Each transaction may have it's own set of

RE: Mem2Mem V4L2 devices [RFC] - Can we enhance the V4L2 API?

2009-10-07 Thread Karicheri, Muralidharan
Marek, As we have seen in the discussion, this is not a streaming device, rather a transaction/conversion device which operate on a given frame to get a desired output frame. Each transaction may have it's own set of configuration context which will be applied to the hardware before starting

RE: Mem2Mem V4L2 devices [RFC] - Can we enhance the V4L2 API?

2009-10-06 Thread Marek Szyprowski
Hello, On October 06, 2009 12:31 AM Karicheri, Muralidharan wrote: Are we constrained to use the QBUF/DQBUF/STREAMON/STREAMOFF model for this specific device (memory to memory)? What about adding new IOCTLs that can be used for this specific device type that possibly can simplify the

Mem2Mem V4L2 devices [RFC] - Can we enhance the V4L2 API?

2009-10-05 Thread Karicheri, Muralidharan
Hi, Are we constrained to use the QBUF/DQBUF/STREAMON/STREAMOFF model for this specific device (memory to memory)? What about adding new IOCTLs that can be used for this specific device type that possibly can simplify the implementation? As we have seen in the discussion, this is not a