Hi Javier, hi Jeongtae,
Please see my comments below.
> -Original Message-
> From: javier Martin [mailto:javier.mar...@vista-silicon.com]
> Sent: 15 March 2012 15:31
> To: Kamil Debski
> Cc: Sakari Ailus; linux-media@vger.kernel.org
> Subject: Re: [Q] media: V4L2 com
Hi Kamil, Sakari,
thank you for your replies.
On 15 March 2012 14:19, Kamil Debski wrote:
> Hi Javier, Sakari,
>
>> From: Sakari Ailus [mailto:sakari.ai...@iki.fi]
>> Sent: 15 March 2012 12:04
>>
>> Hi Javier,
>>
>> (Cc Kamil.)
>>
>> On Wed, Mar 14, 2012 at 12:22:43PM +0100, javier Martin wrote:
Hi Javier, Sakari,
> From: Sakari Ailus [mailto:sakari.ai...@iki.fi]
> Sent: 15 March 2012 12:04
>
> Hi Javier,
>
> (Cc Kamil.)
>
> On Wed, Mar 14, 2012 at 12:22:43PM +0100, javier Martin wrote:
> > Hi,
> > I'm developing a V4L2 mem2mem driver for the codadx6 IP video codec
> > which is include
Hi Javier,
(Cc Kamil.)
On Wed, Mar 14, 2012 at 12:22:43PM +0100, javier Martin wrote:
> Hi,
> I'm developing a V4L2 mem2mem driver for the codadx6 IP video codec
> which is included in the i.MX27 chip.
>
> The capture interface of this driver can therefore return h.264 or
> mpeg4 video frames.
>
Hi,
I'm developing a V4L2 mem2mem driver for the codadx6 IP video codec
which is included in the i.MX27 chip.
The capture interface of this driver can therefore return h.264 or
mpeg4 video frames.
Provided that the size of each frame varies and is unknown to the
user, how is the driver supposed t
