As of today, NVK is now a conformant Vulkan 1.3 implementation on Turing (RTX 2000 and GTX 1600 series), Ampere (RTX 3000 series), and Ada (RTX 4000 series) GPUs.
It does not directly affect wayland support in any way unless you’re using one of those experimental Wayland in Vulkan modes.
It does affect it indirectly insofar as that, with NVK, you’re able to use the nouveau kernel module which exposes standardised interfaces that Wayland relies on without losing the ability to do Vulkan which was not possible previously. If you wanted Vulkan previously, you had to use Nvidia’s proprietary driver and its non-standard interfaces that cause issues with Wayland.
What the… they’re working so fast!!! At this pace, NVK could probably equal, if not surpass the proprietary drivers by the end of the year!
Only 1 question: how will that affect Wayland support for Nvidia?
I’m an AMD user, but I’m curious.
It does not directly affect wayland support in any way unless you’re using one of those experimental Wayland in Vulkan modes.
It does affect it indirectly insofar as that, with NVK, you’re able to use the nouveau kernel module which exposes standardised interfaces that Wayland relies on without losing the ability to do Vulkan which was not possible previously. If you wanted Vulkan previously, you had to use Nvidia’s proprietary driver and its non-standard interfaces that cause issues with Wayland.
Doesn’t Zink on NVK support fully compliant OpenGL 4.6?
Yes but I don’t see how that’s related to Wayland as nouveau (mesa OGL) is also capable of driving apps inside a modern desktop.