https://bugs.freedesktop.org/show_bug.cgi?id=97353
--- Comment #12 from Kristian Høgsberg <[email protected]> ---
(In reply to Tomek Bury from comment #11)
> (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.
Which compositor is this? From a quick look at weston, it looks like it unrefs
the EGLImages when a new wl_buffer is attached, but maybe there's some subtlety
in the ref-counting there.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
wayland-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
