Announcement

Collapse
No announcement yet.

The Grinch That Stole The Radeon Gallium3D Performance?

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

  • #16
    Originally posted by FireBurn View Post
    Sigh

    Phoronix - where articles ARE the bug reports
    Bug reports that generate revenue maintain the tester's income and interest, as well as awareness in the community. In the graphics community a lot of the developers read Phoronix so the message isn't being lost (as evidence, it looks like they already found this regression).

    Kudos Michael.

    Comment


    • #17
      Originally posted by Michael View Post
      The regressed commits should be published on Christmas.
      Don't you actually mean this is an R300g issue, which does not include support for any RadeonHD models?

      I notice you didn't check out r600g, which does support all the RadeonHD models.

      Also worth a mention but not really a big issue is r100 and r200, but those cards are so old that I doubt anyone using them is running anything too stressful on the GPU.

      Comment


      • #18
        yes great work ! you are a hero

        Comment


        • #19
          Originally posted by zwastik View Post
          Gallium 3d developers have implemented more and more features to their drivers and that is great, but sometimes I think that this has been at the cost of performance (which is far behind proprietary drivers).
          I don't think the developers knowingly implement anything which hurts performance, except in cases where frequently used cases are sped up at the expense of a less common case which gets slowed down.

          It's more likely that the developers implemented a new feature, application runtime logic saw the new feature and used it, but for that particular application/card/driver combination using the new feature is actually slower than running without the feature. Game developers do often put heuristics in which help to choose the right code paths depending on GPU/CPU/driver but they tend to be backward looking and have trouble dealing with a driver that is constantly evolving.

          Originally posted by zwastik View Post
          Also, I am curious of how much attention do older hardware drivers get. Maybe this is not an issue for some, but here in third world countries we run a lot of older hw in our machines.
          Since open source developers often start as users who "get fed up and decide to take matters into their own hands" I imagine you will see more developers appearing in those areas as well. Open source projects tend to be "self correcting" that way, although the high learning curve for GPU drivers does make it harder for new developers to step in as existing developers move onto other projects.

          Comment


          • #20
            Just export LIBGL_DRIVERS_PATH=/path/to/mesa-source/lib and then export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$LIBGL_DRIVERS_PA TH. There's no need for LD_PRELOAD. Then, you don't have to 'make install'.
            Free Software Developer .:. Mesa and Xorg
            Opinions expressed in these forum posts are my own.

            Comment


            • #21
              Originally posted by FireBurn View Post
              Sigh

              Phoronix - where articles ARE the bug reports
              Phoronix - where there _are_ articles about r300g.

              Comment

              Working...
              X