Hi Pekka, > I suppose the compositor-side copy of buffers you mentioned is for the > lack of release fences, not acquire fences? Yes, the lack of release fences is the very reason for the copy. I could cook something up for the acquire fence, but that wouldn't synchronise the buffer access anyway. The only way I can be sure the client doesn't overwrite a buffer still in use by the GPU was to texture from a copy and let the compositor release the original without waiting for the GPU and without a fence.
Cheers, Tomek
_______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
