Thank you.
If I am working on both the user side and the driver itself, why the
buffer must contain a full image? Is that a limitation of v4l2 m2m
framework?
On Wed, Mar 19, 2014 at 12:22 AM, Hans Verkuil wrote:
> On 03/19/2014 12:18 AM, m silverstri wrote:
>> I am using v4l2 m2m framework to
On 03/19/2014 12:18 AM, m silverstri wrote:
> I am using v4l2 m2m framework to develop a resize driver. I have an
> image , pass it to the driver and it generated a resize output image.
>
> My v4l2 sequence is
> 1. qbuf OUTPUT, CAPTURE
> 2. stream on OUTPUT, CAPTURE
> 3. dqbuf OUTPUT, CAPTURE
> 4.
I am using v4l2 m2m framework to develop a resize driver. I have an
image , pass it to the driver and it generated a resize output image.
My v4l2 sequence is
1. qbuf OUTPUT, CAPTURE
2. stream on OUTPUT, CAPTURE
3. dqbuf OUTPUT, CAPTURE
4. stream off OUTPUT, CAPTURE
this works if i have a full fra
