Announcement

Collapse
No announcement yet.

Legacy Radeon Gallium3D Performance Drops On Mesa 9.2

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

  • Legacy Radeon Gallium3D Performance Drops On Mesa 9.2

    Phoronix: Legacy Radeon Gallium3D Performance Drops On Mesa 9.2

    It's been a while since delivering any benchmarks from legacy ATI/AMD Radeon hardware like the X1000 (R500) series on Linux. However, with the release of Mesa 9.2 from late August, here are new benchmarks of the Radeon X1000 series GPUs on the open-source Radeon "R300g" Gallium3D graphics driver.

    http://www.phoronix.com/vr.php?view=19106

  • #2
    Control Panel

    We as users need an easy way to turn on/off the various forms of anti-aliasing, for those who may not want or need to use it, or for older cards such as this which struggle to use it anyways.

    Comment


    • #3
      same applies to Intel GM945 Graphics. its now OpenGL 2.1 capable, but slow as hell. everything with some sort of blurr is a pain in the *** alt+tab, i.e. power button or the usual way to turn off the laptop.

      slightly off topic but: would it make sense for newer CPUs for instance (or GM945 users) to compile, kernel and mesa (and with it hopefully the llvmpipe) via apt-build to provide all the power your CPU can offer? Why apt build? Simply to provide a simple and automated way to install self-compiled binaries?
      Last edited by jakubo; 09-13-2013, 10:13 AM.

      Comment


      • #4
        regression?

        Can be used PTS to track commit causing this? As user of r300g, I'm interested in this.

        Comment


        • #5
          Originally posted by halfmanhalfamazing View Post
          We as users need an easy way to turn on/off the various forms of anti-aliasing, for those who may not want or need to use it, or for older cards such as this which struggle to use it anyways.
          When you say easy, do you mean via a GUI? Could simply set GALLIUM_MSAA. See MLAA for how to set MLAA, which uses driconf. I don't think you can set MSAA levels via driconf.

          Note to Michael: when running pre/post mesa 9.2, set GALLIUM_MSAA environment variable to 0, please.

          Comment


          • #6
            Originally posted by FourDMusic View Post
            Note to Michael: when running pre/post mesa 9.2, set GALLIUM_MSAA environment variable to 0, please.
            It won't help. GALLIUM_MSAA can only be used to enable MSAA if MSAA is disabled. If an app enables MSAA, GALLIUM_MSAA has no effect.

            Comment


            • #7
              Originally posted by marek View Post
              It won't help. GALLIUM_MSAA can only be used to enable MSAA if MSAA is disabled. If an app enables MSAA, GALLIUM_MSAA has no effect.
              thanks for the clarification!

              Comment


              • #8
                Clearly we need a disable toggle then, preferably via driconf

                Comment


                • #9
                  Forcing MSAA off might break some apps, because MSAA adds a couple of neat features like alpha-to-coverage and sample mask, and disabling MSAA would also disable the features.

                  In other words, if you want to disable MSAA, fix the phoronix test profiles.

                  Comment


                  • #10
                    That only works if the app offers the choice to disable it. If it only offers autodetection...

                    Comment

                    Working...
                    X