[Wayland-bugs] [Bug 97353] Wayland lacks cross-process synchronisation

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=97353

--- Comment #11 from Tomek Bury <tomek.bury at gmail.com> ---
(In reply to Kristian Høgsberg from comment #10)
> Again, this is implicit (and it really should've been documented better,
> sorry), but the idea is that the compositor communicates its intention to
> texture from the wl_buffer by creating the EGLImage for the wl_buffer. Once
> it's done, it destroys the EGLImage. So once the EGLImage is created you
> have to wait on the client-rendering-finished fence before first use, Once
> the EGLImage is destroyed you signal the compositor-texturing-finished fence.

That's not the case, at least in the latest compositor. Now compositor keeps
EGL images for the lifetime of a client and assumes that writes from client and
reads from the compositor will be implicitly interlocked, the eglImageCreate()
and eglImageDestroy() happens only once per buffer and can't be a driver hook
point to create fences.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20160816/eea28f0e/attachment-0001.html>