Announcement

Collapse
No announcement yet.

AMD Posts Latest Open-Source Linux Patches For FreeSync / Adaptive-Sync / VRR

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

  • AMD Posts Latest Open-Source Linux Patches For FreeSync / Adaptive-Sync / VRR

    Phoronix: AMD Posts Latest Open-Source Linux Patches For FreeSync / Adaptive-Sync / VRR

    One of the few features not yet provided by the mainline open-source Radeon Linux graphics driver will soon be crossed off the list... FreeSync / Adaptive-Sync / HDMI Variable Refresh Rate support...

    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
    How will that blacklisting work with something like games in Wine that use fullscreen Window rather than fullscreen mode?

    Comment


    • #3
      It's a shame Intel and Nvidia doesn't support FreeSync / Adaptive-Sync / VRR.

      Comment


      • #4
        Originally posted by shmerl View Post
        How will that blacklisting work with something like games in Wine that use fullscreen Window rather than fullscreen mode?
        Apart from minimizing behavior, there should be no difference between the two on Xorg. Compositors should be turned off for fullscreen gaming (which happens automatically with Mutter, unless told otherwise by the app).

        Edit: Now that I'm writing about it: I haven't yet tested whether wine borderless tells Mutter to leave compositing on or not.
        Last edited by aufkrawall; 11 October 2018, 06:05 PM.

        Comment


        • #5
          Originally posted by uid313 View Post
          It's a shame Intel and Nvidia doesn't support FreeSync / Adaptive-Sync / VRR.
          IME, whatever intel is doing in their driver results in an exceptionally smooth experience, with less tearing than either AMD or NVidia. NVidia does support their own proprietary 'G-sync' which is similar to AMD's FreeSync. But of course it's all closed and proprietary, so self-respecting FOSS geeks shouldn't be using NVidia hardware anyways.

          Comment


          • #6
            Originally posted by aufkrawall View Post
            Compositors should be turned off for fullscreen gaming (which happens automatically with Mutter, unless told otherwise by the app).
            Fullscreen games do provide a hint that KWin recognizes and it turns compositing off on X (not sure what it's doing on Wayland for it). But I noticed that it doesn't happen with Wine fullscreen window in KDE. So I suspect same issue can affect adaptive sync.

            Comment


            • #7
              Imho this is a good example why that particular KWin design choice is quite stupid.
              I suggest using Compton instead with auto unredirect.

              Comment


              • #8
                Originally posted by uid313 View Post
                It's a shame Intel and Nvidia doesn't support FreeSync / Adaptive-Sync / VRR.
                In 2015 Intel said they planned to support VESA Adaptive Sync (ie FreeSync by another name) though not when. We've not heard anything more about that for a few years so there was a recent argument on another forum with some people claiming there had never been such a plan, so someone got Intel to confirm they still intend to do this with a future hardware generation.

                https://www.reddit.com/r/hardware/co...ure_coming_in/

                Comment


                • #9
                  Good, now if AMD can also release a 1080TI beater (even by %5 is enough) GPU then we be smooth sailing

                  Comment


                  • #10
                    Where did he found Iceweasel in this time and age ... that does not exist anymore:

                    + </application> + <application name="Iceweasel" executable="iceweasel"> + <option name="adaptive_sync_enable" value="false" /> + </application>
                    https://lists.freedesktop.org/archiv...er/205885.html

                    Processes in Debian are firefox-esr (default) or release of firefox (optional), since FF 45, 2.5 years ago, blah, blah

                    I dunno how they think this would work, Debian rename binaries so that two of the same does not exist, while Mozilla for their builds/binaries don't (any branch builds are the same name firefox) Also for games shipped within distro there is a clause how these must start first time in a window, basically nothing starts in fullscreen

                    May i ask here AMD, as corporations gets their harassment-free and developers gets their harassment-free... when will users get their harassment-free?
                    Last edited by dungeon; 11 October 2018, 09:26 PM.

                    Comment

                    Working...
                    X