<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c10">Comment # 10</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 <a class="email" href="mailto:krh@bitplanet.net" title="Kristian Høgsberg <krh@bitplanet.net>"> Kristian Høgsberg</a> <pre>(In reply to Tomek Bury from <a href="show_bug.cgi?id=97353#c9">comment #9</a>) > (In reply to Tomek Bury from <a href="show_bug.cgi?id=97353#c8">comment #8</a>) > > (In reply to Kristian Høgsberg from <a href="show_bug.cgi?id=97353#c4">comment #4</a>) > > Not sure why it got posted twice (and both times with a typo). > I meant: Where do you propose to create the compositor-side fence? I.e. > fence that marks the end of compositor-side reads from the buffer. 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>