On Fri, Sep 24, 2021 at 5:30 PM Jan Ekström wrote:
>
> On Fri, Sep 24, 2021 at 12:06 PM Ho Ming Shun wrote:
> >
> > MMAL is an fundamentally an asynchronous decoder, which was a bad fit
> > for the legacy dataflow API. Often multiple packets are enqueued before
> > a flood of frames are returned
On Fri, Sep 24, 2021 at 12:06 PM Ho Ming Shun wrote:
>
> MMAL is an fundamentally an asynchronous decoder, which was a bad fit
> for the legacy dataflow API. Often multiple packets are enqueued before
> a flood of frames are returned from MMAL.
>
> The previous lockstep dataflow meant that any del
MMAL is an fundamentally an asynchronous decoder, which was a bad fit
for the legacy dataflow API. Often multiple packets are enqueued before
a flood of frames are returned from MMAL.
The previous lockstep dataflow meant that any delay in returning packets
from the VPU would cause ctx->queue_decod
