Announcement

Collapse
No announcement yet.

R600 Gallium3D Shader Compiler Milestone Hit

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

  • R600 Gallium3D Shader Compiler Milestone Hit

    Phoronix: R600 Gallium3D Shader Compiler Milestone Hit

    Beyond working on a R600/700 winsys as well as a command submission checker for these ATI Radeon HD 2000/3000/4000 series graphics processors, Jerome Glisse of Red Hat has also been busy at work on a shader compiler for the R600/700 ASICs with the still-in-early-development Gallium3D driver. Over the weekend Jerome hit one of his first milestones with this code. As Jerome mentions on his blog, the shader compiler is still beginning to work: as in a tri-flat being rendered using this new compiler infrastructure...

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

  • #2
    Finally some love for R600+ cards!

    With so much going on on R300g and almost no R600 commits for ages I was starting to doubt my decision to buy ATI.

    Comment


    • #3
      I can hardly wait for r600g. Especially if the gsoc project for opengl 3.2 will really happen.

      Are there any plans to make the r300g be the default driver? (Say in Mesa 7.9.) Or that's not going to happen until gallium3d 1.0?

      Comment


      • #4
        Originally posted by monraaf View Post
        Finally some love for R600+ cards!

        With so much going on on R300g and almost no R600 commits for ages I was starting to doubt my decision to buy ATI.
        Mesa is not the only project where development is happening. There's the DDX, Kernel DRM and other stuff.

        Comment


        • #5
          Nice! My last video card was an r300 and I think the work on that has been pretty much exhausted. I have an r700 now and glad to see someone working on my card. Hope performance gets up to or even exceeds Windows performance (exceed perhaps by being more flexible and configurable).

          Keep at it!

          Comment


          • #6
            Sincere congrat's on the pretty triangle, but...

            How long until I can run Doom 3, Nexuiz, Google Earth, X3, Jack Keane, & the Penumbra series etc. with open source drivers on an r600+ at max settings? Ever?

            Comment


            • #7
              Originally posted by alazyworkaholic View Post
              How long until I can run Doom 3, Nexuiz, Google Earth, X3, Jack Keane, & the Penumbra series etc. with open source drivers on an r600+ at max settings? Ever?
              When you're too old to bother with that stuff

              Comment


              • #8
                Originally posted by alazyworkaholic View Post
                How long until I can run Doom 3, Nexuiz, Google Earth, X3, Jack Keane, & the Penumbra series etc. with open source drivers on an r600+ at max settings? Ever?
                It's a black triangle.

                Comment


                • #9
                  Originally posted by alazyworkaholic View Post
                  How long until I can run Doom 3, Nexuiz, Google Earth, X3, Jack Keane, & the Penumbra series etc. with open source drivers on an r600+ at max settings? Ever?
                  Doom 3, Nexuiz, and Penumbra work already on the classic Mesa driver in Mesa 7.8.

                  I haven't tested the other ones, but I suspsect they'll work.

                  However last I checked the shadows are messed up in Doom 3, so I had to disable them. And the performance isn't that great. I'd say Doom 3 and Prey were getting about 20-30fps on Medium/High. I didn't benchmark them; but they were playable.

                  Edit: Thanks for the Gallium work Jerome.

                  Comment


                  • #10
                    Originally posted by pvtcupcakes View Post
                    And the performance isn't that great. I'd say Doom 3 and Prey were getting about 20-30fps on Medium/High. I didn't benchmark them; but they were playable.
                    lol

                    Comment


                    • #11
                      Gallium was expected be at 60-70% of the fglrx driver, am I right? Or was it 60-70% slower?

                      And Doom3 getting 20-30fps is enough for single player, but with which card?

                      Prey is running a heavily modified id Tech 4 engine and should squezes out more fps...

                      But where is the performance bottleneck in the Gallium3D? Is it in the kernel memmory management, the OpenGL Mesa state tracker and/or the Gallium drivers themselves (as in what exposes the API?)

                      I hope it isn't in the last one, because then big speed gains can be won across the entire board of graphic cards...

                      Comment


                      • #12
                        Originally posted by pvtcupcakes View Post
                        However last I checked the shadows are messed up in Doom 3, so I had to disable them. And the performance isn't that great. I'd say Doom 3 and Prey were getting about 20-30fps on Medium/High. I didn't benchmark them; but they were playable.
                        which gpu?

                        Comment


                        • #13
                          Originally posted by V!NCENT View Post
                          Gallium was expected be at 60-70% of the fglrx driver, am I right? Or was it 60-70% slower?
                          i think it was bridgman who said, they were hoping to achieve 60 to 70 % of the fglrx speed.
                          but i think this will suffice for most people + you will probably have a comparable performance while runnning a game AND having compositing activated since, the fglrx driver have a steep performance drop in that area.
                          or at least thats what i experienced.

                          Comment


                          • #14
                            Originally posted by Pfanne View Post
                            which gpu?
                            Radeon 4850

                            Comment


                            • #15
                              Originally posted by V!NCENT View Post
                              Gallium was expected be at 60-70% of the fglrx driver, am I right? Or was it 60-70% slower?
                              As I recall it, the 60-70%-as-fast figure Bridgman quoted was prior to CONFIG_BREAK_ALL_GRAPHICS=y and Gallium becauae of fundamental architecture flaws. No?

                              Comment

                              Working...
                              X