Announcement

Collapse
No announcement yet.

Mesa / Gallium3D Branch Happenings

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

  • Mesa / Gallium3D Branch Happenings

    Phoronix: Mesa / Gallium3D Branch Happenings

    Not only are Mesa developers -- those at VMware and within the open-source community -- busy at work on producing new state trackers (such as for OpenCL and OpenGL 3.1/3.2 support) and actual hardware drivers (or virtual drivers), but the core Gallium3D architecture and API continues to be revised as well. Over the past few days there have been some new Gallium3D branches that have come about and others that are getting ready to be merged to master, or enter the mainline Mesa code-base. Just this morning the Gallium3D pipe-format-simplify branch was opened up by VMware, which cleans up the pipe format header file...

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

  • #2
    Does this mean that we will be able to use our (Ati) GPUs with Gallium3D in Mesa 7.8? With proper power management, xv, opengl 2, etc. I guess that hardware video decoding, opengl 3.x and opencl will come later.

    Comment


    • #3
      Originally posted by HokTar View Post
      Does this mean that we will be able to use our (Ati) GPUs with Gallium3D in Mesa 7.8?
      nope.
      maybe we will see support for r300, but nothing else.

      Comment


      • #4
        Originally posted by HokTar View Post
        Does this mean that we will be able to use our (Ati) GPUs with Gallium3D in Mesa 7.8? With proper power management, xv, opengl 2, etc. I guess that hardware video decoding, opengl 3.x and opencl will come later.
        power management does not depend on gallium3d. see: http://www.rojtberg.net/271/4-years-later/

        Comment


        • #5
          Libdrm just pushed to distribute today on fedora 12.
          It's like this whole gallium 3d thing is happening very quickly.

          Comment


          • #6
            Originally posted by madman2k View Post
            power management does not depend on gallium3d. see: http://www.rojtberg.net/271/4-years-later/
            I know that, I was just curious if it would work practically out of the box with Gallium3D? (Since it will be in the kernel, so I guess it should not depend on anything else, just the IRQs and of course needs kms.)

            By the way, is there an ETA, or roadmap, or anything when given features should be done? For example would it be a feasible guess to say that we will have this in Lucid+1?
            I'm aware of the radeonwiki and the galliumstatus pages, but I'd like to ask what is still needed to have a working system based on G3D? I mean apart from the ddx drivers what else is necessary?

            Comment


            • #7
              yeah I just installed mesa-git on archlinux

              most games are running without crashing in the limited testing I just did there are texture issues in most games except openarena which i think there still might be a problem or too

              compiz works fine... opengl supported verson is 1.5 shaders are apparently running on the cpu

              this is an r620 aka radeon 4200 I don't see why gallium3d wounldn't be able to surpass catalyst im most repects by mesa 7.8 I am already rather impressed with what they have so far

              Comment


              • #8
                Originally posted by cb88 View Post
                yeah I just installed mesa-git on archlinux

                most games are running without crashing in the limited testing I just did there are texture issues in most games except openarena which i think there still might be a problem or too

                compiz works fine... opengl supported verson is 1.5 shaders are apparently running on the cpu

                this is an r620 aka radeon 4200 I don't see why gallium3d wounldn't be able to surpass catalyst im most repects by mesa 7.8 I am already rather impressed with what they have so far
                There's no r600 gallium3d driver yet. Mesa 7.8 just got a lot of smaller r600 commits today, so maybe checkout and rebuild it and see if it fixes your problems. You can also try experimental GLSL support today but don't expect it to run stable just yet.

                Comment


                • #9
                  Is there a software rendering driver usable at this time ? The Gallium 3D documentation is quite obscure on that point.
                  all it tells is :

                  The softpipe driver is a software implementation of the Gallium3D interface.

                  It will be used as a reference implementation and as a fallback driver when a hardware driver isn't available. The softpipe driver will make extensive use of run-time code generation to efficiently execute vertex, fragment and rasterization operations.
                  So as far I understand, you can use Gallium 3D with any graphic card and if the driver don't support a feature the software rendering pipe will take care of it. That's it ?

                  Comment


                  • #10
                    Originally posted by Xheyther View Post
                    Is there a software rendering driver usable at this time ? The Gallium 3D documentation is quite obscure on that point.
                    all it tells is :



                    So as far I understand, you can use Gallium 3D with any graphic card and if the driver don't support a feature the software rendering pipe will take care of it. That's it ?
                    I don't think that's quite accurate. You have to use either the software rendering (softpipe driver) or use a hardware accelerated driver. The other drivers won't automatically fall back to using software rendering for missing features unless that's been specifically added into the driver by the devs. What the quote above is saying is that if you have a card without a gallium driver (like r100 or r800) then you can still use software accelerated 3D.

                    Comment


                    • #11
                      It's looking like Fedora is ironing out the basics and 2d stuff on this and ubuntu will come in and iron out some of the 3d stuff. This is all going to be up and running probably in 5 months. 3d textures will probably be terrible for a while though. I keep searching all over the gallium and DRI pages and everything is getting knocked out pretty fast. I don't think I'll even mess with binary blobs on Fedora 12.

                      Comment


                      • #12
                        Originally posted by smitty3268 View Post
                        What the quote above is saying is that if you have a card without a gallium driver (like r100 or r800) then you can still use software accelerated 3D.
                        Because without acceleration, we would have to use... software? I'm sure there's slower and faster ways of doing it, but the expression doesn't make sense. Anyway, from what I've understood pushing data back and forth between the GPU doing one bit and the CPU doing other bits can be a performance killer in itself negating much of the benefits.

                        Comment


                        • #13
                          I think the main use of the softpipe driver is as a "reference" platform so that (a) upper level functionality can be built and tested without having to wait for hardware drivers, and (b) if there is a question about the behaviour of a specific hw driver it can be compared to the softpipe reference rather than having to find different hardware for A/B testing.

                          From a user point of view, however, unless there is a good hw driver for your card then you shouldn't be planning to use Gallium3D, although the llvmpipe driver might be turn out to be interesting if you have a big honkin' CPU and weak graphics.

                          Comment


                          • #14
                            Originally posted by bridgman View Post
                            From a user point of view, however, unless there is a good hw driver for your card then you shouldn't be planning to use Gallium3D, although the llvmpipe driver might be turn out to be interesting if you have a big honkin' CPU and weak graphics.
                            While I understand this, I'd like to ask what is needed to be done in order to have a Linux distro running atop Gallium3D? Of course apart from the ddx drivers. (Yes, I asked earlier, but got no reply. Maybe second time.)

                            Comment


                            • #15
                              If you just want to get the complete stack running on your system, I guess you need :

                              - relatively complete winsys and pipe drivers for your hardware (even softpipe needs a winsys driver),
                              - mesa built with Gallium3D enabled and using the pipe driver,
                              - a kernel supporting KMS for your hardware
                              - the st/xorg X driver

                              The list above is what you would need to use G3D for both X and 3D. If you just want 3D, then you only need the first 2.

                              For a Linux distro to use Gallium3D by default, I don't think anything else is required other than some proven history of it actually working.

                              Since Gallium3D is targetted at shader-based chips (R300 and up for ATI/AMD hardware) the distro will still need logic to use a hardware-specific X driver with older GPUs, so presumably that same logic could deal with the case where r300g (the 3xx-5xx Gallium3D driver) was ready to go but 600g (6xx+) was not.

                              Comment

                              Working...
                              X