Announcement

Collapse
No announcement yet.

R600/700 Mesa Driver Picks Up Blit Support

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

  • R600/700 Mesa Driver Picks Up Blit Support

    Phoronix: R600/700 Mesa Driver Picks Up Blit Support

    While a blitter module was introduced for Gallium3D that uses the 3D engine for blitting, this doesn't help those without blit support that are still running the "classic" Mesa driver stack. Over the night, however, blit support has arrived for the ATI R600/700 Mesa driver...

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

  • #2
    Well, it didn't totally come over night. First Alex created r600_blit.c some time ago. Then Andre Maasikas picked up his work and made blit actually work in his tree http://cgit.freedesktop.org/~andrem/...g/?h=r600-blit

    Finally his patches were merged to one patch and hit Mesa's master branch.

    Comment


    • #3
      Is this why my glxgears fps went from ~800 to 1800 overnight? Pretty cool

      (4870 HD w/ KMS/DRI2, zen-sources 2.6.33, gentoo)

      I don't suppose it will ever rival fglrx until the distant future when gallium3D is maybe working with r700

      Comment


      • #4
        great news ! this should make 2D even faster (compared to fglrx it's already much faster but it can't be fast enough )

        now we need some decent Evergreen support and I finally can migrate to the opensource drivers (again) - yay !

        Comment


        • #5
          Not 2D only. For example OpenArena with Bloom goes up from 1FPS to 30FPS

          http://bugs.freedesktop.org/show_bug.cgi?id=25723

          Comment


          • #6
            from 1 to 30 ?

            now that's what I call acceleration

            seems in the past most of the graphics stuff still went through the cpu ...

            Comment


            • #7
              These guys are good!

              Have anyone tried Apple HD trailer playback with 720p and 1080p?

              Comment


              • #8
                Yeah playing around with this after recompiling, all of my 2D stuff is like butter! Better acceleration really improves the feel of the desktop.

                Comment


                • #9
                  Originally posted by Phoronix
                  This proper blitter support should result in performance improvements for both 2D and 3D acceleration.
                  These commits are all in Mesa. I don't see how this is going to have any effect on 2D performance. Please enlighten me

                  Comment


                  • #10
                    Maybe 2D with a compositor running (where the compositor uses 3D) ?

                    Comment


                    • #11
                      Yeah that could make sense.

                      Comment


                      • #12
                        Originally posted by bridgman View Post
                        Maybe 2D with a compositor running (where the compositor uses 3D) ?
                        yeah, especially compiz and kwin with compositing

                        all the newer chips don't have "native" 2D support or acceleration support anymore if I remember right - so bit blitting which is mainly targeted at the 3D engine / helping it to operate autonomously should improve both 2D and 3D (both are "run" or accelerated by the 3D engine)

                        Comment


                        • #13
                          I guess the point others were trying to make is that the X driver has had 2D blit code (using the 3D *hardware*) for a long time - what's new is making more use of blit code in the 3D *driver* (which would not affect 2D operations done by the X driver).

                          There was a blit routine in drm for a while, but it was only used for GLSwapBuffers AFAIK; now presumably other functions are being accelerated as well.

                          Comment


                          • #14
                            The blit code in mesa accelerates glCopyTex(Sub)Image and could also be used to accelerate glReadPixels. It's pretty much the same code as used by EXA for copies and the drm for buffer moves and textures uploads.
                            Last edited by agd5f; 01-16-2010, 11:43 AM.

                            Comment


                            • #15
                              Great, another stinkin' GL command I have to go and understand

                              Comment

                              Working...
                              X