https://bugs.kde.org/show_bug.cgi?id=405912
--- Comment #9 from oiaohm <oia...@gmail.com> --- (In reply to Shmerl from comment #8) > Wayland applications aren't supposed to be restricted to EGL. They can use > WSI too (VK_USE_PLATFORM_WAYLAND_KHR and etc.). Again that path does not have required sync functionality in wayland. When wayland was design EGL existed and Vulkan did not. Reality here what you pass wl_buffer that is a platform particular buffer not in fact defined in wayland protocol. Platform particular buffer contains all you sync stuff. How to process platform particular contents of the wl_buffer that has to be sorted out but that is not a wayland protocol problem. Wayland protocol is not a network server protocol like X11. Its local protocol. Being a local protocol it can have platform particular things where it implemented.. Really this is not a wayland extension. This would really be how does EGL use Vulkan buffers and how does Vulkan use EGL buffers and extract required information. Wayland protocol particularly designed not to need changing just because a new sync system is made. Drivers get updates and maintain compatibility with the interfaces they provide everything should work. Basically wayland protocol design should have no place for adaptive sync (FreeSync) because this is a platform particular thing and should in the wl_buffer where all other platform particular things should be. So basically this problem should fall on mesa, nvidia and other graphics driver vendors to design the implementation. This one is a big change of the Wayland design. Don't have the compositor/wayland protocol inventing wheels to solve issues that should be solved at khronos.org. Graphics drivers makes really should be able to advise/design how all this sync stuff works so it works the best because they understand the hardware. -- You are receiving this mail because: You are watching all bug changes.
