Le vendredi 19 juillet 2019 à 14:45 +0900, Tomasz Figa a écrit :
> On Wed, Jul 17, 2019 at 9:18 PM Nicolas Dufresne wrote:
> > Hello,
> >
> > there is one little detail/proposal, see inline .
> >
> > Le lundi 03 juin 2019 à 13:28 +0200, Hans Verkuil a écrit :
> > > From: Tomasz Figa
> > >
> >
On Wed, Jul 17, 2019 at 9:18 PM Nicolas Dufresne wrote:
>
> Hello,
>
> there is one little detail/proposal, see inline .
>
> Le lundi 03 juin 2019 à 13:28 +0200, Hans Verkuil a écrit :
> > From: Tomasz Figa
> >
> > Due to complexity of the video decoding process, the V4L2 drivers of
> > stateful
Hello,
there is one little detail/proposal, see inline .
Le lundi 03 juin 2019 à 13:28 +0200, Hans Verkuil a écrit :
> From: Tomasz Figa
>
> Due to complexity of the video decoding process, the V4L2 drivers of
> stateful decoder hardware require specific sequences of V4L2 API calls
> to be foll
Le lundi 15 juillet 2019 à 14:12 +0200, Maxime Jourdan a écrit :
> On Tue, Jun 11, 2019 at 10:29 AM Hans Verkuil
> wrote:
> > On 6/10/19 9:54 PM, Nicolas Dufresne wrote:
> > > Hi Hans,
> > >
> > > I went through it, and I think we are close to ready. Unfortunately, I
> > > believe the SOURCE_CHA
On Tue, Jun 11, 2019 at 10:29 AM Hans Verkuil wrote:
>
> On 6/10/19 9:54 PM, Nicolas Dufresne wrote:
> > Hi Hans,
> >
> > I went through it, and I think we are close to ready. Unfortunately, I
> > believe the SOURCE_CHANGE event is still under specified. There was a
> > post recently to try and ad
On 7/10/19 10:23 AM, Tomasz Figa wrote:
> On Wed, Jul 10, 2019 at 5:09 PM Hans Verkuil wrote:
>>
>> On 7/3/19 6:58 AM, Tomasz Figa wrote:
>>> Hi Hans,
>>>
>>> On Mon, Jun 3, 2019 at 8:28 PM Hans Verkuil
>>> wrote:
From: Tomasz Figa
Due to complexity of the video decoding pro
On Wed, Jul 10, 2019 at 5:09 PM Hans Verkuil wrote:
>
> On 7/3/19 6:58 AM, Tomasz Figa wrote:
> > Hi Hans,
> >
> > On Mon, Jun 3, 2019 at 8:28 PM Hans Verkuil
> > wrote:
> >>
> >> From: Tomasz Figa
> >>
> >> Due to complexity of the video decoding process, the V4L2 drivers of
> >> stateful deco
On 7/3/19 6:58 AM, Tomasz Figa wrote:
> Hi Hans,
>
> On Mon, Jun 3, 2019 at 8:28 PM Hans Verkuil wrote:
>>
>> From: Tomasz Figa
>>
>> Due to complexity of the video decoding process, the V4L2 drivers of
>> stateful decoder hardware require specific sequences of V4L2 API calls
>> to be followed.
Hi Hans,
On Mon, Jun 3, 2019 at 8:28 PM Hans Verkuil wrote:
>
> From: Tomasz Figa
>
> Due to complexity of the video decoding process, the V4L2 drivers of
> stateful decoder hardware require specific sequences of V4L2 API calls
> to be followed. These include capability enumeration, initializati
On 6/12/19 8:49 AM, Hans Verkuil wrote:
> On 6/12/19 2:25 AM, Nicolas Dufresne wrote:
>> Le mardi 11 juin 2019 à 10:29 +0200, Hans Verkuil a écrit :
>>> On 6/10/19 9:54 PM, Nicolas Dufresne wrote:
Hi Hans,
I went through it, and I think we are close to ready. Unfortunately, I
be
On 6/12/19 2:25 AM, Nicolas Dufresne wrote:
> Le mardi 11 juin 2019 à 10:29 +0200, Hans Verkuil a écrit :
>> On 6/10/19 9:54 PM, Nicolas Dufresne wrote:
>>> Hi Hans,
>>>
>>> I went through it, and I think we are close to ready. Unfortunately, I
>>> believe the SOURCE_CHANGE event is still under spe
Le mardi 11 juin 2019 à 10:29 +0200, Hans Verkuil a écrit :
> On 6/10/19 9:54 PM, Nicolas Dufresne wrote:
> > Hi Hans,
> >
> > I went through it, and I think we are close to ready. Unfortunately, I
> > believe the SOURCE_CHANGE event is still under specified. There was a
> > post recently to try a
On 6/10/19 9:54 PM, Nicolas Dufresne wrote:
> Hi Hans,
>
> I went through it, and I think we are close to ready. Unfortunately, I
> believe the SOURCE_CHANGE event is still under specified. There was a
> post recently to try and add a new flag for changes in color space
> which is not included her
Hi Hans,
I went through it, and I think we are close to ready. Unfortunately, I
believe the SOURCE_CHANGE event is still under specified. There was a
post recently to try and add a new flag for changes in color space
which is not included here. We are also missing a workflow for changes
that don't
From: Tomasz Figa
Due to complexity of the video decoding process, the V4L2 drivers of
stateful decoder hardware require specific sequences of V4L2 API calls
to be followed. These include capability enumeration, initialization,
decoding, seek, pause, dynamic resolution change, drain and end of
st
15 matches
Mail list logo
