Announcement

Collapse
No announcement yet.

NVIDIA 555.42.02 Linux Beta Brings Wayland Explicit Sync, GSP Firmware Used By Default

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

  • NVIDIA 555.42.02 Linux Beta Brings Wayland Explicit Sync, GSP Firmware Used By Default

    Phoronix: NVIDIA 555.42.02 Linux Beta Brings Wayland Explicit Sync, GSP Firmware Used By Default

    It's coming a week later than anticipated but the NVIDIA R555 Linux driver beta has been released! This is the NVIDIA proprietary Linux driver update that brings Wayland explicit sync support along with a host of other important improvements...

    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
    I'm happy to see startups like NVIDIA catch up to AMD

    On a serious note, explicit sync benefits the entire ecosystem. There's a lot of people who fough for this for years and I'm really glad it's finally here
    Last edited by Kjell; 21 May 2024, 01:06 PM.

    Comment


    • #3
      A great milestone for sure, but unfortunately Wayland still lacks several important features 16 years into its existence.
      • No standard accessibility stack (almost every accessibility feature is broken and Freedesktop themselves admit it),
      • No standard input method protocols (KDE's own David Edmudson has admitted none of the *six* input method protocols are good enough),
      • Portals are a mess (see the DRM leasing fiasco in GNOME),
      • There's still no push-to-talk support (global shortcuts was supposed to fix this, wasn't it? So how come it's not fixed?),
      • There's still no cursor warping (needed by several CAD and 3D modelling programs)
      • Autotype from password managers is impossible to implement because of Wayland's "security" model (Wayland was designed for embedded, not desktop),
      • Session restore and colour management are still nowhere to be seen despite both being worked on for over 4 years now
      • Recovering from crashes is still only supported by KDE 6 and Qt 6 - GNOME thinks it's "absolutely stupid" to have a reliable desktop apparently, and wlroots continue to just sit on the sidelines doing nothing about it either
      • Windows still can't set their own icons (protocol for this was trashed by GNOME, of course)
      And myriad other problems...

      Comment


      • #4
        Bah, Arch doesn't pick up betas, I will have to wait a little bit longer.
        Though tbh the biggest Wayland offender lately hasn't been Nvidia. It's been Chromium.

        Comment


        • #5
          So, what is the excuse now to not use Wayland? Even NVIDIA is doing their part.

          Comment


          • #6
            Originally posted by Hazel View Post
            So, what is the excuse now to not use Wayland? Even NVIDIA is doing their part.
            Because it can't do basic shit by design, such as querying window absolute positions, or positioning them, or parenting a process' window inside of another app as a child (YES EVEN IF BOTH APPS PERMIT EACH OTHER!).

            Broken by design.

            Comment


            • #7
              Originally posted by Hazel View Post
              So, what is the excuse now to not use Wayland?
              nvidia-settings doesn't work

              Comment


              • #8
                It can do those things, it's a matter of permissions.

                Security by design.

                Comment


                • #9
                  Originally posted by Hazel View Post
                  It can do those things, it's a matter of permissions.

                  Security by design.
                  No it can't. Stop shilling and coping so hard without checking facts.

                  The missing Wayland protocols for features that are available in X11 (but are denied by the official Wayland protocols) - probonopd/wayland-x11-compat-protocols

                  For those picking up on this as "news", please read the following list: PCSX2 still supports Wayland. It just prefers the XCB/XWayland platform by default. You can set the I_WANT_A_BROKEN_WAYLAND_...

                  Wayland can't access window positions. From what I can tell this is an intentional limitation and there aren't ways to access this information. This means functions such as `WM_window_find_under_cursor` doesn't work. From the user perspective the following functionality wont work. - "Swap Area...


                  There's way more but I will trigger the spam filter unfortunately.

                  Comment


                  • #10
                    Originally posted by Hazel View Post
                    ... Security by design.
                    The windowing system is not the place to restrict what applications are and are not allowed to do.

                    If you want to restrict what applications can do, use a sandbox (or disallow these protocols in your compositor via a configuration setting).
                    ‚Äč

                    Comment

                    Working...
                    X