<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - We need fences support in Wayland compositors" href="https://bugs.freedesktop.org/show_bug.cgi?id=98766#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - We need fences support in Wayland compositors" href="https://bugs.freedesktop.org/show_bug.cgi?id=98766">bug 98766</a> from <a class="email" href="mailto:tomek.bury@gmail.com" title="Tomek Bury <tomek.bury@gmail.com>"> Tomek Bury</a> <pre>> We can create an EGLSync object, request that it be signalled when the most > recently submitted command has fully retired, and then use the Android > native_fence_fd extension to get a dma-fence from that. That's not guaranteed to work. It's hard to tell what type file descriptor you'll get from VK or EGL. It can be either the old-style Android fence fd or new-style sync file fd. Vulkan 1.1 says this: "Handles of type VK_EXTERNAL_SEMAPHORE_HANDLE_TYPE_SYNC_FD_BIT generated by the implementation may represent either Linux Sync Files or Android Fences at the implementation’s discretion. Applications should only use operations defined for both types of file descriptors, unless they know via means external to Vulkan the type of the file descriptor, or are prepared to deal with the system-defined operation failures resulting from using the wrong type." The EGL_ANDROID_native_fence_sync extension is even more vague and only says that you'll get a "file descriptor that refers to a native fence object". It means different things on different Android versions but this is Wayland, not Android.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>