As pointed out in This Week in GNOME, there’s been some continued work on Variable Rate Refresh for the GNOME desktop. The VRR setting within GNOME Settings continues to be iterated on as the developers iron out how they’d like to present the Variable Rate Refresh setting for users. The developers have been discussing how to best present the option as to avoid confusion as well as how it makes the most technical sense as far as the option goes.

Edit: “Variable Refresh Rate - Roadmap” - https://gitlab.gnome.org/GNOME/mutter/-/issues/3125

    • SmoochyPit@beehaw.orgEnglish
      9·
      11 months ago

      I think the compositor, Mutter in Gnome’s case, has to explicitly request VRR from the display driver via the Wayland protocol. So it’s a bit of each.

      • ZamundaaaEnglish
        7·
        11 months ago

        via the Wayland protocol

        There’s no Wayland protocol involved, Mutter directly talks to the kernel

        • SmoochyPit@beehaw.orgEnglish
          3·
          11 months ago

          Ah, I see, thank you for the correction. Does Wayland only encompass communication between clients and the server? I’ve seen some code calling the wlroots functions for requesting VRR and some of how the Nvidia open kernel modules respond. Is requesting VRR a part of Kernel Mode Setting, then?

          • ZamundaaaEnglish
            4·
            11 months ago

            Does Wayland only encompass communication between clients and the server?

            Yes

            Is requesting VRR a part of Kernel Mode Setting, then?

            Also yes

    • Vash63@lemmy.world
      4·
      11 months ago

      It is an X thing. Wayland is a protocol not a display server though, so for Wayland the Wayland compositor has to implement it (Mutter in this case)