[Bug 711155] wayland: add wl_drm support to wayland sink

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=711155

Benjamin Gaignard <benjamin.gaignard at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #265552|needs-work                  |none
             status|                            |
 Attachment #265552|0                           |1
        is obsolete|                            |

--- Comment #40 from Benjamin Gaignard <benjamin.gaignard at gmail.com> ---
Created attachment 310472
  --> https://bugzilla.gnome.org/attachment.cgi?id=310472&action=edit
make waylandsink support wl_dmabuf protocol

I attach an updated version of the patch.

Even it is not using the upstreamed wayland dmabuf protocol it show how we can
use dmabuf in pool allocator to perform zero-copy.
With this patch we have been able to use SW and HW (v4l2) decoders, transform,
and encoder in STB context.
We have done playbacks of local and live streams, transcoding and video mixing
(glmixer + Mali) by using this way of dealing with dmabuf in pool.
We also have use SW elements (for video mixing and color enhancement) between
HW elements using dmabuf without issues.

The next step is to do the same with the upstreamed wayland dmabuf protocol.

@slomo, @tim, @daniel: I would like to have your opinion of how we should
implement and use dmabuf in gstreamer. Can we continue to negotiate it as a
memory type in pool's allocator ?
>From what I experimented since more a year this solution works well and allow
to mix SW and HW elements.
For me Nicolas's solution will reduce the compatibility between SW and HW
elements because add dmabuf in caps will not allow to graph elements freely
even if SW could fairly use dmabuf.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.