why release_buffer is not required in the GstDroidBufferPool?
from my understanding, release_buffer is opposite to alloc_buffer; when we
"++dpool->num_buffers" in alloc_buffer, should we "--dpool->num_buffers" in
release_buffer?
__
人：Mohammed Hassan
收件人：Sailfish OS Developers
主题：Re: [SailfishDevel] 回复：Re: 回复：Re:
could_we_support_hw_overlay_from_gst-droid?
日期：2015年05月22日 20点42分
On Fri, 22 May 2015 16:31:35 +0800
Halley wrote:
> after a thought, I think overlay can be added back in the following
> way:1. waylan
after a thought, I think overlay can be added back in the following way:1.
wayland-android-client-protocol.h supports passing ANativeWindowBuffer from
wayland client to server.2. An object(WindowSurface) with same interface of
ANativeWindow can be constructed in host; which meets the requiremen
I don't have much idea on it as well.
I think EGLImage or texture id are concept inside one process, not able to
shared between two process (wayland client and wayland server). for EGL
application, drm buffer name is passed by wayland-drm protocol inside libEGL.
some global buffer handle are req
ffer (mem), eglImgAttrs);
- 原始邮件 -
发件人：Mohammed Hassan
收件人：Halley
抄送人：Sailfish OS Developers
主题：Re: could we support hw overlay from gst-droid?
日期：2015年04月29日 08点27分
On Sun, Apr 26, 2015 at 02:23:24PM +0800, Halley wrote:
> Hi Mohammed:
>
> in gst
Hi Mohammed:in gst-droid, eglsink is created for texture video rendering.is
it possible that the video is rendered to overlay? independent from egl/gles.
___
SailfishOS.org Devel mailing list
To unsubscribe, please
