Announcement

Collapse
No announcement yet.

XWayland Sees Updated Protocol Support To Help WLROOTS & KDE

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

  • XWayland Sees Updated Protocol Support To Help WLROOTS & KDE

    Phoronix: XWayland Sees Updated Protocol Support To Help WLROOTS & KDE

    X.Org Server 1.21's XWayland implementation has added support for the xdg-output-unstable-v1 version 3 protocol to help the likes of KDE and compositors like Sway based on WLROOTS...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    In Xwayland there's some interesting stuff happening. On one site fixes for XWayland on demand (https://gitlab.freedesktop.org/xorg/..._requests/203/) and, more exiting for gamers, mode setting emulation (https://gitlab.freedesktop.org/xorg/...e_requests/270). The second one is not as pressing any more than before we had Proton, but it allows legacy native and wine games to run in smaller resolutions than the actual screen, scaling up the output (like it is done in proton).

    Comment


    • #3
      Kde is a mess on the Wayland protocol integration above all as for Nvidia users.

      Comment


      • #4
        Originally posted by Azrael5 View Post
        Kde is a mess on the Wayland protocol integration above all as for Nvidia users.
        KDE doesn't run the greatest for AMDGPU users with Wayland either.

        Comment


        • #5
          Originally posted by Azrael5 View Post
          Kde is a mess on the Wayland protocol integration above all as for Nvidia users.
          There is a far worse mess for Nvidia drivers. If you watched the recent debconf 19 on secure UEFI boot there is no clear plan on how to support Nvidia binary drivers in secure boot mode. So going forwards for Linux users will be AMD or Intel if you don't want to be beating your head against a brick wall.

          Comment


          • #6
            Isn't it possible to release xwayland independently from the complete xorg? It doesn't make sense that Wayland depends that much from xorg releases!

            Comment


            • #7
              Originally posted by skeevy420 View Post

              KDE doesn't run the greatest for AMDGPU users with Wayland either.
              So, KDe is equally a mess .

              Comment


              • #8
                Originally posted by R41N3R View Post
                Isn't it possible to release xwayland independently from the complete xorg? It doesn't make sense that Wayland depends that much from xorg releases!
                Indeed, Xwayland is X11, a solution that I consider a scam.

                Comment


                • #9
                  Originally posted by Azrael5 View Post

                  Indeed, Xwayland is X11, a solution that I consider a scam.
                  XWayland is not quite X11.

                  XWayland is a Wayland client which is an X11 server
                  Xephyr is an X11 client which is an X11 server
                  Xorg is a native X11 server, including a lot of the underlying plumbing with the drivers. This same plumbing is used by Wayland. This plumbing is also bigger than Wayland and the networking part of Xorg put together.

                  XWayland, similar to Xvnc also requires a lot of the higher level X11 protocol related stuff so it knows how to talk. Xvnc source is often distributed with a (stripped) Xorg server.

                  Comment


                  • #10
                    It's not KDE's fault. Wayland is far too incomplete a protocol. Remember it took Gnome a decade to get this far, and Mutter is far, far more than just a Wayland implementation, they had to reinvent so much stuff it is literally stupid.

                    Comment

                    Working...
                    X