Announcement

Collapse
No announcement yet.

Mesa 19.1 Enters Feature Freeze In Two Weeks, Releasing Around 21 May

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

  • Mesa 19.1 Enters Feature Freeze In Two Weeks, Releasing Around 21 May

    Phoronix: Mesa 19.1 Enters Feature Freeze In Two Weeks, Releasing Around 21 May

    Juan A. Suarez Romero of Igalia is serving as the release manager for Mesa 19.1 and sent out a reminder on Monday of the planned release schedule for this quarterly driver update...

    http://www.phoronix.com/scan.php?pag...lease-Planning

  • #2
    I bet there is no radv freesync support in several months in the mainline mesa. We need to wait a very long time like with opengl driver. PC gaming is not a top priority of many mesa developers.
    I implemented the same adaptive_sync blacklisting that the opengl driver has. It works, so no reason to block the radv freesync patch.
    https://gitlab.freedesktop.org/mesa/...e_requests/596

    Some other developer should drive the freesync support mainlining, because google is interested speed optimization for chromebooks only.
    https://www.amd.com/en/processors/chromebook
    Last edited by debianxfce; 04-16-2019, 03:44 AM.

    Comment


    • #3
      Originally posted by debianxfce View Post
      I bet...
      Viva Las Vegas



      Some other developer should drive the freesync support mainlining, because google is interested speed optimization for chromebooks only.
      https://www.amd.com/en/processors/chromebook
      Why do you want FreeSync on 6W potatos, these could only maybe play decent games via Stadia in future... and for that fancy features like plain VSync or TearFree is enough
      Last edited by dungeon; 04-16-2019, 06:37 AM.

      Comment


      • #4
        Debianxfce still has no clue why simple blacklisting won't work. Like I explained a few posts ago, it's because compositing is popular and basically done everywhere not xf-shit-ce debian. Post patches to all the compositors and add other whitelist to the drive, or fuck off. There's no middle. There's no other solutions. You do it right, it not at all.

        Comment


        • #5
          Originally posted by abott View Post
          Debianxfce still has no clue why simple blacklisting won't work.
          You junior have no clue. The radv freesync blacklist patch is almost a 1:1 copy paste from the opengl version. Because you have no clue, here is the current blacklist file for applications, desktops and compositors.
          https://gitlab.freedesktop.org/mesa/...-defaults.conf

          Originally posted by abott View Post
          Post patches to all the compositors and add other whitelist to the drive, or fuck off.
          Fck yourself off, none of compositors uses vulkan. Software that need vulkan freesync blacklisting do not exists yet and its the application user/developers responsibility to add to the blacklist like in the opengl case:
          https://gitlab.freedesktop.org/mesa/...2160ad5d59012b
          Last edited by debianxfce; 04-16-2019, 11:27 AM.

          Comment


          • #6
            @debianxfce

            An update on your RQ from Bas:
            "Developer
            FWIW I have a more polished version of adaptive sync + config at !672"

            Comment


            • #7
              Originally posted by nuetzel View Post
              @debianxfce
              An update on your RQ from Bas:
              "Developer
              FWIW I have a more polished version of adaptive sync + config at !672"
              KISS. It is not polished, more clever is to minimize code and have support for the intel driver with the same code.
              Last edited by debianxfce; 04-17-2019, 06:56 AM.

              Comment

              Working...
              X