<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Wayland lacks cross-process synchronisation"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97353#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Wayland lacks cross-process synchronisation"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97353">bug 97353</a>
from <span class="vcard"><a class="email" href="mailto:tomek.bury@gmail.com" title="Tomek Bury <tomek.bury@gmail.com>"> <span class="fn">Tomek Bury</span></a>
</span></b>
<pre>(In reply to Kristian Høgsberg from <a href="show_bug.cgi?id=97353#c10">comment #10</a>)
<span class="quote">> 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.</span >
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>