Announcement

Collapse
No announcement yet.

AMD's Catalyst Working On A GLSL Shader Cache

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

  • AMD's Catalyst Working On A GLSL Shader Cache

    Phoronix: AMD's Catalyst Working On A GLSL Shader Cache

    There's a lot of work going on right now to the AMD Catalyst Linux graphics driver. We've written about new features coming to an upcoming Catalyst Linux driver but silently being pushed into the latest round of release is a GLSL shader disk cache...

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

  • #2
    XDG

    Maybe they should follow the XDG specification and put it somewhere under ~/.cache/

    Comment


    • #3
      I wish AMD would just move all their resources to foss drivers development instead of confusing users and developers with two separate drivers each with it's own set of cons and pros.

      Comment


      • #4
        Originally posted by uid313 View Post
        Maybe they should follow the XDG specification and put it somewhere under ~/.cache/
        AMD, please read this!

        Comment


        • #5
          Originally posted by gutigen View Post
          I wish AMD would just move all their resources to foss drivers development instead of confusing users and developers with two separate drivers each with it's own set of cons and pros.
          AMD, please read this!

          Comment


          • #6
            More transparency from the Catalyst devs is cool
            Scrapping the closed driver entirely would be even cooler (but probably too cool to happen )

            Comment


            • #7
              Originally posted by gutigen View Post
              I wish AMD would just move all their resources to foss drivers development instead of confusing users and developers with two separate drivers each with it's own set of cons and pros.
              That's kind of happening soon with the kernel module etc.

              The OpenGL driver is obviously a different team and not directly affiliated with the Linux Catalyst Team and it needs to exist anyway (e.g. for Windows).

              Comment


              • #8
                Originally posted by d2kx View Post
                That's kind of happening soon with the kernel module etc.

                The OpenGL driver is obviously a different team and not directly affiliated with the Linux Catalyst Team and it needs to exist anyway (e.g. for Windows).
                I meant Catalyst Linux team to ditch Catalyst and move to foss team - few months of work with Mesa devs and community and we would have the best GPU drivers ever (judging by amount of progress just few Mesa guys can pull in such short amount of time)

                Comment


                • #9
                  Yes, they SHOULD follow the XDG specs? Developers keep on polluting our home dirs, it?s really annoying.

                  Comment


                  • #10
                    Something as obvious as shader caching is only being done now??

                    Also,
                    Originally posted by gutigen View Post
                    I wish AMD would just move all their resources to foss drivers development instead of confusing users and developers with two separate drivers each with it's own set of cons and pros.
                    the FOSS driver will never beat the binary blob in performance, because FOSS tries to be "fair" in that it's not optimized for specific games and usages, but rather tries to get the best average performance in all use cases. Catalyst (as well as Nvidia's, or any competitive GPU driver) has specific "profiles" for high end games that tune the driver behavior specifically to this game's behavior (ie. a compilation of game specific hacks so to speak). This could mean something as simple as optimized buffer allocations, or as crazy as shutting down entire parts of the pipeline if they're not used by the game.

                    Comment

                    Working...
                    X