<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - EGL client behaviour too undefined" href="https://bugs.freedesktop.org/show_bug.cgi?id=98731#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - EGL client behaviour too undefined" href="https://bugs.freedesktop.org/show_bug.cgi?id=98731">bug 98731</a> from <a class="email" href="mailto:jadahl@gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>(In reply to Pekka Paalanen from <a href="show_bug.cgi?id=98731#c1">comment #1</a>) > Where should this specification live? Good question. I don't think we mention any of wayland-egl.h in any extension specification. At least not in <a href="https://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_platform_wayland.txt">https://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_platform_wayland.txt</a> Would it be enough to just add it to wayland-egl.h? > > Do we need the same for Vulkan? The Vulkan version of wayland-egl.h, VK_KHR_wayland_surface, already some documententation about this: "... Also, calling vkQueuePresentKHR will result in Vulkan sending wl_surface.commit requests to the underlying wl_surface of each VkSwapchainKHR objects referenced by pPresentInfo. Therefore, if the application wishes to synchronize any window changes with a particular frame, such requests must be sent to the Wayland display server prior to calling vkQueuePresentKHR." Given the wording about being able to synchronize any window changes, one could probably assume that "wl_surface.commit" will ONLY be sent as a result of calling VkQueuePresentKHR. As the buffer allocation is more explicit in Vulkan, I assume those issues as well are not present there.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>