Announcement

Collapse
No announcement yet.

NVIDIA EGLStreams Support Merged Into KWin For KDE Plasma 5.16

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • NVIDIA EGLStreams Support Merged Into KWin For KDE Plasma 5.16

    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?pag...rged-KWin-5.16

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

    Comment


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

      Comment


      • #4
        Sad

        Comment


        • #5
          Originally posted by tildearrow
          standard
          EGL_KHR_stream is a standard https://www.khronos.org/registry/EGL...KHR_stream.txt

          Comment


          • #6
            Originally posted by xpue View Post
            A standard almost controlled entirely by NVIDIA. They only got it as a "standard" to convince us.

            Comment


            • #7
              Originally posted by xpue View Post
              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.

              Comment


              • #8
                Originally posted by dos1 View Post
                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.
                Last edited by xpue; 04-15-2019, 12:48 PM.

                Comment


                • #9
                  Originally posted by tildearrow
                  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.
                  ​​​

                  Comment


                  • #10
                    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.

                    Comment

                    Working...
                    X