Hi Laurent,
On Mon, Nov 12, 2012 at 12:18:10PM +0100, Laurent Pinchart wrote:
> On Sunday 11 November 2012 10:51:06 Sakari Ailus wrote:
> > On Mon, Nov 05, 2012 at 09:47:00PM +0100, Sylwester Nawrocki wrote:
> > > On 11/05/2012 11:45 AM, Alain VOLMAT wrote:
> > > > Hi Laurent,
> > > >
> > > > Yes
Hi Sakari,
On Sunday 11 November 2012 10:51:06 Sakari Ailus wrote:
> On Mon, Nov 05, 2012 at 09:47:00PM +0100, Sylwester Nawrocki wrote:
> > On 11/05/2012 11:45 AM, Alain VOLMAT wrote:
> > > Hi Laurent,
> > >
> > > Yes indeed, meta plane seems a good candidate. It was the other option.
> > >
> > >
Hi Sylwester,
On Mon, Nov 05, 2012 at 09:47:00PM +0100, Sylwester Nawrocki wrote:
> Hi,
>
> On 11/05/2012 11:45 AM, Alain VOLMAT wrote:
> >Hi Laurent,
> >
> >Yes indeed, meta plane seems a good candidate. It was the other option.
> >
> >The pity with that is that the FMT can thus no longer be sta
Hi Sylwester,
On Monday 05 November 2012 21:47:00 Sylwester Nawrocki wrote:
> On 11/05/2012 11:45 AM, Alain VOLMAT wrote:
> > Hi Laurent,
> >
> > Yes indeed, meta plane seems a good candidate. It was the other option.
> >
> > The pity with that is that the FMT can thus no longer be standard FMT
Hi,
On 11/05/2012 11:45 AM, Alain VOLMAT wrote:
Hi Laurent,
Yes indeed, meta plane seems a good candidate. It was the other option.
The pity with that is that the FMT can thus no longer be standard FMT but
a specific format that include both plane 0 with real frame data and plane
1 with meta
do things and a
second format that has 2 planes
Regards,
Alain
> -Original Message-
> From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
> Sent: Sunday, November 04, 2012 12:54 PM
> To: Alain VOLMAT
> Cc: linux-media
> Subject: Re: Way to request a tim
Hi Alain,
On Wednesday 31 October 2012 14:21:30 Alain VOLMAT wrote:
> Hi all,
>
> We have developed a V4L2 mem2mem driver for an H264 encoder running on an IP
> of one of our SoC and would like to have one more v4l2_buffer flag value
> for that.
>
> In the context of this driver, we discovered t
Hi all,
We have developed a V4L2 mem2mem driver for an H264 encoder running on an IP of
one of our SoC and would like to have one more v4l2_buffer flag value for that.
In the context of this driver, we discovered that the current V4L2 encode API
is missing the feature to mention to the IP that
