Problem with etnaviv and gstreamer 1.0

Nicolas Dufresne nicolas.dufresne at collabora.com
Tue Dec 5 19:10:11 UTC 2017


Le mardi 05 décembre 2017 à 17:06 +0000, Luís Mendes a écrit :
> On Tue, Dec 5, 2017 at 4:17 PM, Nicolas Dufresne
> <nicolas.dufresne at collabora.com> wrote:
> > Le mardi 05 décembre 2017 à 16:07 +0000, Luís Mendes a écrit :
> > > > > making the CODA VPU unit available to all the applications
> > > > > that are
> > > > > already VAAPI and VDPAU aware, like vlc, kodi and others.
> > > > > That way
> > 
> > FFMPEG, Khodi and other applicaitons (Chromium, GStreamer) already
> > support this type of decoder. It's a state full decoder, while
> > VAAPI is
> > designed for state less decoders. It also make not sense to wrap
> > this
> > inside a GPU driver, because it's not a GPU.
> 
> If you look into mesa you will find that it implements the VAAPI and
> VDPAU APIs and that i965, amdgpu and nouveau drivers implement the
> bridge through the VL internal mesa API. In ubuntu the resulting
> dynamic libraries from mesa compilation will be packaged into
> mesa-va-drivers and mesa-vdpau-drivers. So, yes the VPU
> implementations are side-by-side with the GPU support.

I know this very well. It make sense for Intel, AMD and NVidia driver,
because the CODEC (which are just accelerators) are tightly coupled
with the GPU. These are also state less CODEC.

On the other hand, the CODA IP is not coupled with the GPU and is state
full. The VAAPI (and the deprecated VDPAU interfaces) are not designed
to support state full decoder, and the extra indirections does not
provide much benefit.

Nicolas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/etnaviv/attachments/20171205/a3fb6018/attachment-0001.sig>


More information about the etnaviv mailing list