2 ms·
Currently running Gnome from a Wayland session with Nvidia's 510.39.01 drivers without issue. It's not Wayland that's not ready yet, it's the ecosystem around i
by myownfriend 5y ago
Currently running Gnome from a Wayland session with Nvidia's 510.39.01 drivers without issue. It's not Wayland that's not ready yet, it's the ecosystem around it.
While the first commit on the Wayland git was in 2008, it's client and server APIs weren't considered stable until 2013 and then DE support for it only really picked up in 2016 since they were built around X11 from the beginning.
If you were an Nvidia user then your options for DEs were limited to the ones that supported EGLStreams and you didn't get XWayland hardware acceleration or support for Webrender in Firefox until Nvidia started support DMA-buf in June of last year. Nvidia didn't support GBM until October of this year but it had an annoying memory leak which caused issues with programs not wanting to launch of launching as black squares. On top of that, the code that compositors and XWayland used to detect whether to use GBM or EGLStreams didn't work at first and XWayland windows launched as transparent so they needed to be updated. It wasn't until these beta drivers, which came out this month, that I'm able to do everything I'm supposed to be able to do in a Wayland session and the major hurdles in Wayland adoption on Nvidia have been removed. Kwin already removed it's EGLStreams backend because it never worked well to begin with and the drivers will only improve from now on.