Announcement

Collapse
No announcement yet.

R600 Open-Source Driver WIth GLSL, OpenGL 2.0

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

  • R600 Open-Source Driver WIth GLSL, OpenGL 2.0

    Phoronix: R600 Open-Source Driver WIth GLSL, OpenGL 2.0

    If Catalyst 9.12 for Linux and its changes didn't deliver on what you wanted for your Christmas wishes, perhaps this change to their open-source driver does deliver on one of your hopes. The ATI R600/700 open-source 3D stack should now be OpenGL 2.0 compatible (compared to OpenGL 1.5 previously) and the GLSL (GL Shading Language) support should be "mostly" completed. AMD's Richard Li recently introduced a commit that enables GL2 and there has been other AMD/ATI 3D work going on too...

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

  • #2
    Shouldn't Gallium Core Drive for R600-R800 be changed from TODO to WIP? That is what VMware is working on, right?

    And perhaps HDMI Audio for R600/R700 from WIP to Mostly or Done?

    Comment


    • #3
      Then show me a video with gl2benchmark, Zero Ballistics and maybe HoN working with it without problems. Till that happens opengl 2 is only on paper not more.

      Comment


      • #4
        Originally posted by Kano View Post
        Then show me a video with gl2benchmark, Zero Ballistics and maybe HoN working with it without problems. Till that happens opengl 2 is only on paper not more.
        thats probably, why it says "mostly"...
        most of the work is done, but it still doesn't do anything
        but i did see some nice furmark screenshots.

        Comment


        • #5
          I don't think it's ready to be used really. But then again it's only enabled in master, let's hope that most of the bugs will be fixed by the time mesa 7.8 is released

          Comment


          • #6
            This is awesome! I wonder if it can become on par with fglrx If/when it gets the optimizations done, that would be really nice.

            Comment


            • #7
              Sooo.. just to sum it up: R600+ can choose between radeon and fglrx if they want (useable) 3d accel (--> GLSL) and <=R500 users have to use an old fglrx? Is this correct? *THUMBS UP* to ATi.. definately my last ati/amd board..

              Comment


              • #8
                Originally posted by Louise View Post
                Shouldn't Gallium Core Drive for R600-R800 be changed from TODO to WIP? That is what VMware is working on, right?
                AFAIK the VMWare folks are primarily working on (a) the Gallium3D driver for their emulated SVGA hardware, and (b) the non-driver portions of the Gallium3D framework (ie Mesa, Xorg, GL, VG, CL etc... state trackers along with refining the internal APIs).

                Corbin (MostAwesomeDude) mentioned that he was starting on a Gallium3D driver for 6xx-8xx but that's all I have heard. Richard is looking forward to working on Gallium3D as well; best guess is that will happen after (a) some testing / fixing on 6xx-7xx GLSL, and (b) getting inital 3D engine support working on Evergreen.

                Originally posted by Louise View Post
                And perhaps HDMI Audio for R600/R700 from WIP to Mostly or Done?
                I suspect it's still treated as "WIP" because the first patches are just working their way into the kernel tree now and haven't had much general testing there. It probably is coming up on time to switch to "Mostly" though...

                Originally posted by Dragonix View Post
                Sooo.. just to sum it up: R600+ can choose between radeon and fglrx if they want (useable) 3d accel (--> GLSL) and <=R500 users have to use an old fglrx? Is this correct? *THUMBS UP* to ATi.. definately my last ati/amd board..
                Huh ? Where are you getting that ?

                GLSL was enabled in the Gallium3D driver for 3xx-5xx *before* it was enabled in the classic mesa driver for 6xx-7xx. Neither one is ready for general use yet, both are being tested and fixed. Richard enabled GLSL so that application testing could *start* (including making sure that enabling GLSL didn't cause previously working games to break), not because the work was *finished*.
                Last edited by bridgman; 12-19-2009, 12:21 PM.

                Comment


                • #9
                  And where's the work on GLSL and OpenGL 2.0 on Mesa for R300-R500 cards? Is it something about the same level or more/less advanced?

                  Comment


                  • #10
                    bridgman already answered your question, Xeros. GLSL support for r300-500 cards is in about the same state, or slightly further progressed.

                    Comment


                    • #11
                      The Gallium3D driver for 3xx-5xx already has GLSL and GL 2.1 enabled, and that's where all the development work is happening.

                      I believe the shader compiler still needs some work for flow control instructions, but initial impression is that they don't actually get used very much.

                      Comment


                      • #12
                        Originally posted by xeros View Post
                        And where's the work on GLSL and OpenGL 2.0 on Mesa for R300-R500 cards? Is it something about the same level or more/less advanced?
                        Don't know how far it is. But before this becomes yet another thread full of complaints from owners of pre-R600 cards. I suggest you all take a look at the git logs, there are far more commits for r300/r300g and more people working on r300/r300g than there are on r600.

                        Comment


                        • #13
                          Originally posted by bridgman View Post
                          Richard enabled GLSL so that application testing could *start* (including making sure that enabling GLSL didn't cause previously working games to break), not because the work was *finished*.
                          Unfortunately, is *does* break some games. Quake Live for example runs dead slow with GLSL enabled, I assume it's using the software renderer. From what I have experienced in the past regarding Mesa-git updates, this will be fixed sooner than I could imagine.

                          Comment


                          • #14
                            Thanks for replies. I've read about R300 work with Gallium3D but I wanted to know what of that has been already backported(?) to Mesa as it it's going to distributions sooner than Gallium3D.

                            Comment


                            • #15
                              I don't understand all the. Oh it's not going to come soon. Or it's not going to happen soon. These people have been working on this junk for YEARS. It's not like it's just getting off the ground or anything. I mean i read blogs about this stuff 2 years ago. I'll be shocked if it's not 90 percent done and Opengl 3.0 compatible in 6 months.

                              Comment

                              Working...
                              X