Re: [PATCH 1/2] vicodec: Have decoder propagate changes to the CAPTURE queue

2018-10-26 Thread Tomasz Figa
On Fri, Oct 19, 2018 at 10:00 PM Ezequiel Garcia wrote: > > On Fri, 2018-10-19 at 09:14 +0200, Hans Verkuil wrote: > > On 10/18/2018 06:08 PM, Ezequiel Garcia wrote: > > > The decoder interface (not yet merged) specifies that > > > width and height values set on the OUTPUT queue, must > > > be pro

Re: [PATCH 1/2] vicodec: Have decoder propagate changes to the CAPTURE queue

2018-10-19 Thread Ezequiel Garcia
On Fri, 2018-10-19 at 09:14 +0200, Hans Verkuil wrote: > On 10/18/2018 06:08 PM, Ezequiel Garcia wrote: > > The decoder interface (not yet merged) specifies that > > width and height values set on the OUTPUT queue, must > > be propagated to the CAPTURE queue. > > > > This is not enough to comply w

Re: [PATCH 1/2] vicodec: Have decoder propagate changes to the CAPTURE queue

2018-10-19 Thread Hans Verkuil
On 10/18/2018 06:08 PM, Ezequiel Garcia wrote: > The decoder interface (not yet merged) specifies that > width and height values set on the OUTPUT queue, must > be propagated to the CAPTURE queue. > > This is not enough to comply with the specification, > which would require to properly support st

[PATCH 1/2] vicodec: Have decoder propagate changes to the CAPTURE queue

2018-10-18 Thread Ezequiel Garcia
The decoder interface (not yet merged) specifies that width and height values set on the OUTPUT queue, must be propagated to the CAPTURE queue. This is not enough to comply with the specification, which would require to properly support stream resolution changes detection and notification. Howeve