Announcement

Collapse
No announcement yet.

R600 Gallium3D Can Now Do OpenGL 3.0, GLSL 1.30

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

  • R600 Gallium3D Can Now Do OpenGL 3.0, GLSL 1.30

    Phoronix: R600 Gallium3D Can Now Do OpenGL 3.0, GLSL 1.30

    Marek Olk has made another exciting commit to the Mesa mainline Git repository this weekend... What he's accomplished now is making it possible to successfully advertise OpenGL 3.0 / GLSL 1.30 support within the R600 Gallium3D driver for the Radeon HD 2000 series and later...

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

  • #2
    Thank you Marek (and thank you Michael)! I'm waiting for an update of oibaf's drivers to test OpenGL 3.0 features with my AMD 6570

    Comment


    • #3
      just awesome

      but why is this not in mesa 8.0 ? ? ? this irritate me a little bit.

      Comment


      • #4
        Is this actually adding full gl3 functionality, or merely advertising gl3 for debugging/testing purposes?

        Comment


        • #5
          Originally posted by Qaridarium View Post
          just awesome

          but why is this not in mesa 8.0 ? ? ? this irritate me a little bit.
          Talk on IRC suggested that it might get included in 8.0 or possibly released as 8.0.1.

          Comment


          • #6
            WAHOO!!! MERCI Devs!!

            (glxinfo output)
            Code:
            OpenGL vendor string: X.Org
            OpenGL renderer string: Gallium 0.4 on AMD JUNIPER
            OpenGL version string: 3.0 Mesa 8.0-devel (git-672ad90)
            OpenGL shading language version string: 1.30

            Comment


            • #7
              we've had debugging enables for ages, look at the recent r600 commit history, where we've been finishing off all the underneath GL3.0 stuff

              The big items left are:

              EXT_transform_feedback needs upstream kernel patch, and it currently locks up on all R700 class hardware.

              cayman needs some more work to finish off a few integer opcodes (divide/mod).

              Its got 7620/7846 on piglit on my rv635 right now, a few of the remaining issues should be solved by Jerome's tiling work.

              Comment


              • #8
                There are some OpenGL 3.0 demos at http://es.g0dsoft.com/?page_id=236

                Comment


                • #9
                  "The R600g driver now joins Intel Sandy Bridge, Gallium3D Softpipe, and Nouveau NVC0-Fermi ..."

                  Does this mean, with all the support from AMD, nouveau got there first?

                  Comment


                  • #10
                    Originally posted by madbiologist View Post
                    There are some OpenGL 3.0 demos at http://es.g0dsoft.com/?page_id=236
                    "GPU Raytracer" these demos are not really openGL3.0 LOL but yes they need openGL3.0

                    Comment


                    • #11
                      Wow! Congratulations and THANK YOU to everyone who made it possible!

                      Better powersaving management and my 4200+6650 will be shine with opensource drivers.

                      Comment


                      • #12
                        Can we please document all these various environment variables somewhere? As a driver tester I hate having to dig through the source to find these, and it's not every time that Michael documents which env vars he uses when he posts articles (sometimes he just says "a flag" and doesn't mention which one), and of course they aren't in any of the documentation.

                        A better way would be to ship a /etc/mesa-debug.conf config file in /etc with a simple var=value format, but only ship and read from that file if mesa is compiled in debug mode (i.e. with debug symbols etc). Might need an option like --enable-debug-conf in configure. Then, ship a default mesa-debug.conf that briefly documents all possible settings but leave them commented out, so the user can easily uncomment and change them as desired.

                        This method would also remove the need for the user to hack environment variables into the pipeline before starting X, because it seems that you might get strange behavior if some of your mesa-using programs are running with the flags, and some without. Especially e.g. tiling...

                        Comment


                        • #13
                          It's pretty easy to find these: grep debug_get_bool_option *

                          Anyway, going to all that trouble for something that's a, likely to disappear once these features are finished and b, only of interest to a very small number of people seems like a waste of time.

                          Comment


                          • #14
                            Originally posted by whizse View Post
                            It's pretty easy to find these: grep debug_get_bool_option *

                            Anyway, going to all that trouble for something that's a, likely to disappear once these features are finished and b, only of interest to a very small number of people seems like a waste of time.
                            Setting up the debug configuration infrastructure would be a one-time investment. Anyone who wants to write a debug option into their code afterwards would still be calling ONE function; it's just that the name of the function would be different from "debug_get_bool_option". Or maybe, heck, we could change the implementation of that function to DO exactly what I've proposed.

                            Then of course they'd have to write something like this:

                            #Enable GLSL 1.30 support on Radeon 2xxx or later
                            #R600_GLSL130=1

                            in the mesa-debug.conf.example file, but that would take about 3 seconds of a developer's valuable time Can't have that.

                            Comment


                            • #15
                              There's already drirc for that.

                              Comment

                              Working...
                              X