VOOZH about

URL: https://www.phoronix.com/news/GNOME-51-Drops-EGLStreams

⇱ GNOME 51 Retires Legacy NVIDIA Driver Support With Removing EGLStreams - Phoronix


👁 Phoronix

GNOME 51 Retires Legacy NVIDIA Driver Support With Removing EGLStreams

Written by Michael Larabel in NVIDIA on 5 June 2026 at 06:28 AM EDT. 19 Comments
EGLStreams was NVIDIA's original route to supporting Wayland with their official Linux graphics driver stack. Adoption was limited and driver vendors outside of NVIDIA didn't end up going with EGLStreams/EGLDevice. Thankfully, NVIDIA corrected course long ago with DMA-BUF, GBM, and KMS support that aligns with the rest of the ecosystem, and now that old code path is being removed from GNOME Mutter.

Jonas Ådahl has removed the EGLStreams/EGLDevice support from Mutter for the upcoming GNOME 51 release. This eliminates legacy NVIDIA driver support but allows for a cleaner codebase in focusing on just the well-tested and widely-used path.
"This removes the code that implements support for using Wayland EGLStreams for client EGL support on Wayland, and using EGLDevice + EGLStream to abstract away KMS page flipping. This has since a long time been replaced with the standard DMA buffer passing protocol in Wayland, and using GBM for buffer allocation and using KMS directly for interacting with the kernel."

This merge hit Mutter Git today for sunsetting that EGLStreams code.

👁 NVIDIA EGLStreams


For those new around here, here is a 2014 article about NVIDIA's Wayland route at the time. Thankfully, a lot has changed since their initial Wayland enablement.

Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter, LinkedIn, or contacted via MichaelLarabel.com.