NVIDIA EGLStreams Support Merged Into KWin For KDE Plasma 5.16

[phoronix]

Phoronix: NVIDIA EGLStreams Support Merged Into KWin For KDE Plasma 5.16

Quite a surprise this Monday morning is finding that KDE's EGLStreams back-end for the KWin Wayland compositor has been merged! The KDE Plasma 5.16 release this summer will thus introduce support for running the KDE Plasma Wayland session with the proprietary NVIDIA Linux driver stack...

http://www.phoronix.com/scan.php?page=news_item&px=EGLStreams-Merged-KWin-5.16

[Azrael5]

FINALLY! So will NVIDIA users be able to take benefit from wayland too?

[Azrael5]

THAT'S THE BEST NEWS OF THE YEAR! If it is true!

[dos1]

Sad

[xpue]

standard

EGL_KHR_stream is a standard https://www.khronos.org/registry/EGL...KHR_stream.txt

[tildearrow]

EGL_KHR_stream is a standard https://www.khronos.org/registry/EGL...KHR_stream.txt

A standard almost controlled entirely by NVIDIA. They only got it as a "standard" to convince us.

[dos1]

EGL_KHR_stream is a standard https://www.khronos.org/registry/EGL...KHR_stream.txt

It's an extension. There are various, sometimes mutually incompatible, extensions out there; some are even used purely to signalize hardware and/or driver capabilities.

[xpue]

It's an extension

ARB_create_context, for example, is also an "extension". But without it opengl 3+ is unavailable for you. Khronos infrastructure is based on extensions.

[Britoid]

This is what happens when you decide to disregard a standard such as GBM (yes, it's been done outside Mesa) and develop your own. You become the one that must provide support since nobody is accepting your method.

By the way, it seems that "Unix Device Memory Allocator" isn't going anywhere...

GBM isn't a standard. It was made specifically for Mesa.

[shmerl]

KWin on Wayland is still not ready, due to:

https://bugs.kde.org/show_bug.cgi?id=387313

https://phabricator.kde.org/T10530

Also, there should be a more focused effort on using Vulkan path for compositors.