[Bug 768794] ion: DMA Buf allocator based on ion

[GStreamer (GNOME Bugzilla)]

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

Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |nicolas at ndufresne.ca

--- Comment #4 from Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> ---
Please click "reply" to reply to questions, so we can understand you.

1) isn't replied
2) isn't replied
3) isn't replied

(In reply to kevin from comment #3)
> Will fix coding style issue.
> 
> GLdownloadelement can propose one GL buffer pool to upstream. The GL buffer
> pool allocate DMA FD memory from ION allocator. and than create one EGL
> image from DMA FD. So upstream can use GL buffer and downstream can use fd
> memory.

Ok, and are you going to implement that ?

> 
> Suppose GLupload also can propose GL buffer pool and dma-buf memory to avoid
> video copy. Is it reasonable?

It's reasonable. In better words, you suggest using this allocator (when
available) in DMABuf importer element like glupload, kmssink, v4l2 m2m,
v4l2sink etc. 

> 
> ion.h is sufficient for build. ion device open will fail when use the ion
> allocator if platform haven't ion driver.

So that's a reply for 4), I guess importer will try to open the device to
decided to use or not this allocator.

Please reply to the other questions.

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