[Bug 699382] v4l2: dmabuf handling is not complete

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=699382
  GStreamer | gst-plugins-good | git

--- Comment #12 from Nicolas Dufresne <nicolas.dufresne at collabora.co.uk> 2014-05-17 02:16:45 UTC ---
As Benjamin mention on IRC, we can play with the presence of the dmabuf
allocator in the query. To decide to export, for upstream pool
(decide_allocation), we'd look if the allocator is proposed in the list of
allocators, if so export (using that allocator). For downstream pool, we'd
offer our own allocator and the dmabuf allocator, and decide to export base on
what has been configured on the pool.

For the import case there is two scenario. When importing from downstream pool
(decide allocator), we would try and find a dmabuf allocator, if we find it,
we'd set that in the config and then import. When buffers comes from upstream,
we can't do that in advance, so we'll have to make the decision on first
buffer. Though, on first frame it's fine to try and fallback, later it will
probably be harder to switch.

Note that code like v4l2 that ignore downstream pool in certain cases will need
to be reviewed, as normally the proposed allocator might be specialised, and
only usable with the associated pool. The allocator with custom allocation
method (unless known) will need to be skipped.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.