Announcement

Collapse
No announcement yet.

Compiz Running With Mesa On R600/700 GPUs

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

  • #46
    Originally posted by agd5f View Post
    you need to checkout the r6xx-r7xx-3d branch:
    git checkout -b r6xx-r7xx-3d origin/r6xx-r7xx-3d
    Now I got the stats that I was looking for

    Code:
    ~/drm$ git diff b48bd 59ed4 --stat
     bsd-core/drm_mode.h          |    1 +
     bsd-core/r600_cp.c           |    1 +
     bsd-core/r600_microcode.h    |    1 +
     bsd-core/radeon/Makefile     |    4 +-
     linux-core/Makefile.kernel   |    2 +-
     linux-core/ati_pcigart.c     |    4 +-
     linux-core/drm_agpsupport.c  |    8 +
     linux-core/drm_compat.h      |    9 +-
     linux-core/drm_fops.c        |    2 +-
     linux-core/drm_memory.c      |    5 +
     linux-core/drm_os_linux.h    |    3 +-
     linux-core/drm_sysfs.c       |    6 +-
     linux-core/drm_vm.c          |    9 +
     linux-core/r600_cmdbuf.c     |    1 +
     linux-core/r600_cp.c         |    1 +
     linux-core/r600_microcode.h  |    1 +
     linux-core/radeon_cs.c       |    1 +
     linux-core/radeon_drv.c      |   10 +-
     shared-core/drm_mode.h       |    2 +
     shared-core/drm_pciids.txt   |  123 +
     shared-core/r600_cmdbuf.c    |  685 ++++
     shared-core/r600_cp.c        | 2545 ++++++++++++
     shared-core/r600_microcode.h | 9025 +++++++++++++++++++++++++++++++++++++++++-
     shared-core/radeon_cp.c      |  391 ++-
     shared-core/radeon_cs.c      |  852 ++++
     shared-core/radeon_drm.h     |   29 +-
     shared-core/radeon_drv.h     |  718 ++++-
     shared-core/radeon_irq.c     |   14 +-
     shared-core/radeon_state.c   |   86 +-
     tests/modeprint/app          |  Bin 16233 -> 0 bytes
     30 files changed, 14405 insertions(+), 134 deletions(-)
    ~/drm$
    Could I have used git to tell me what branches that exist?

    Comment


    • #47
      Originally posted by agd5f View Post
      Newer chips tend build on older ones. Both r6xx and r7xx have a similar programming model, so from the driver's perspective they can share a lot of code. Kind of like r3xx, r4xx, and r5xx.
      I see... Sort of like K10 and K10.5 if we talked CPU's.

      Comment


      • #48
        Originally posted by bridgman View Post
        I don't think the next generation is soon enough to have any differences in DRM vs graphics coupling - the development pipe is 3-4 years long and the top level design is locked down pretty early in the process. I wouldn't be expecting anything in that regard.
        That must put a slight pressure on doing the right thing

        Originally posted by bridgman View Post
        Reusing code from Catalyst probably isn't an option since the internal designs are so different. We did try at the start of the project, but the changes required were big and it turned out to be a lot more work than writing the drivers from scratch.

        On the other hand, writing the open source drivers for the next generation GPUs while the Catalyst work is still relatively fresh in everyones mind is bound to help. That was one of the reasons we ended up getting the acceleration code running on 7xx first (remeber the "first triangle" back in August last year) and then working out the 6xx-7xx differences to get the code working on 6xx as well.
        Impressive that it was possible to make R700 features working without all of the R600, when they are so related.

        Comment


        • #49
          Originally posted by Louise View Post
          Could I have used git to tell me what branches that exist?
          to see a list of remote branches:
          git branch -r

          Comment


          • #50
            Originally posted by agd5f View Post
            to see a list of remote branches:
            git branch -r
            Cool! Thanks.

            I am learning git right now, as you can tell .

            I want to use it for my thesis, where I use Matlab.

            Comment


            • #51
              Using the command 'make' or 'make DRM_MODULES="radeon"' produces this output when attempting to compile agd5f's drm git source code into the kernel:

              make[1]: Entering directory `/usr/src/zen-sources'
              CC [M] /tmp/gitadrm/drm/linux-core/drm_auth.o
              In file included from /tmp/gitadrm/drm/linux-core/drmP.h:85,
              from /tmp/gitadrm/drm/linux-core/drm_auth.c:36:
              /tmp/gitadrm/drm/linux-core/drm_os_linux.h:54: error: conflicting types for 'irqreturn_t'
              include/linux/irqreturn.h:16: note: previous declaration of 'irqreturn_t' was here
              make[2]: *** [/tmp/gitadrm/drm/linux-core/drm_auth.o] Error 1
              make[1]: *** [_module_/tmp/gitadrm/drm/linux-core] Error 2
              make[1]: Leaving directory `/usr/src/zen-sources'
              make: *** [modules] Error 2

              Is the error related to the Zen-sources 2.6.30-zen3 kernel or agd5f's code?

              Comment


              • #52
                Originally posted by charlie View Post
                Using the command 'make' or 'make DRM_MODULES="radeon"' produces this output when attempting to compile agd5f's drm git source code into the kernel:

                make[1]: Entering directory `/usr/src/zen-sources'
                CC [M] /tmp/gitadrm/drm/linux-core/drm_auth.o
                In file included from /tmp/gitadrm/drm/linux-core/drmP.h:85,
                from /tmp/gitadrm/drm/linux-core/drm_auth.c:36:
                /tmp/gitadrm/drm/linux-core/drm_os_linux.h:54: error: conflicting types for 'irqreturn_t'
                include/linux/irqreturn.h:16: note: previous declaration of 'irqreturn_t' was here
                make[2]: *** [/tmp/gitadrm/drm/linux-core/drm_auth.o] Error 1
                make[1]: *** [_module_/tmp/gitadrm/drm/linux-core] Error 2
                make[1]: Leaving directory `/usr/src/zen-sources'
                make: *** [modules] Error 2

                Is the error related to the Zen-sources 2.6.30-zen3 kernel or agd5f's code?
                agd5f wrote earlier in this post that his branch is against 2.6.28 and would port it when the API stabilizes.

                Comment


                • #53
                  But he did already

                  Comment


                  • #54
                    Damn! That was quick

                    Comment


                    • #55
                      I just applied nanonyme's patch. I haven't tested anything newer than 2.6.28 yet, so YMMV...

                      Comment


                      • #56
                        r6xx-r7xx-3d works with kernel 2.6.31-rc5

                        Originally posted by agd5f View Post
                        I just applied nanonyme's patch. I haven't tested anything newer than 2.6.28 yet, so YMMV...
                        hw:
                        01:00.0 VGA compatible controller: ATI Technologies Inc Mobilitiy Radeon HD 3650

                        glxinfo:
                        OpenGL vendor string: Advanced Micro Devices, Inc.
                        OpenGL renderer string: Mesa DRI R600 (RV635 9591) 20090101 TCL
                        OpenGL version string: 1.4 Mesa 7.6-devel

                        ~$ uname -a
                        Linux gandalf 2.6.31-5-generic #24-Ubuntu SMP Sat Aug 1 12:47:58 UTC 2009 x86_64 GNU/Linux
                        ~$ glxgears
                        IRQ's not enabled, falling back to busy waits: 2 16
                        167 frames in 5.0 seconds = 33.252 FPS
                        239 frames in 5.0 seconds = 47.662 FPS

                        So the r6xx-r7xx-3d compiles, installs and runs in 2.6.31. Both compiz and glxgears run, both slowly, but running anyways.

                        Google earth also works, slowly and has a lot of artifacts, but works
                        Last edited by jjjj; 08-04-2009, 02:06 AM.

                        Comment


                        • #57
                          Originally posted by agd5f View Post
                          I just applied nanonyme's patch. I haven't tested anything newer than 2.6.28 yet, so YMMV...
                          Arf! Now how will I resist to completely bork my system once again?... :-)

                          Comment


                          • #58
                            whats the cat obession all about

                            Tigris? Tegra? All the OSX codenames - whats the obession with cats and why did AMD choose a name thats almost identical to Nvidias' rival product?

                            Ceiling cat is watching you AMD/Chipzilla!

                            Comment


                            • #59
                              Originally posted by danboid View Post
                              Tigris? Tegra? All the OSX codenames - whats the obession with cats and why did AMD choose a name thats almost identical to Nvidias' rival product?

                              Ceiling cat is watching you AMD/Chipzilla!
                              you cant blame amd.
                              they tried different stuff with their lowcost notebook platform congo...
                              but suddenly a bunch of idiots thought that its evil to call a notebook platform after a region that "The site has named the African country the most dangerous place in the world to be a female because of the epidemic of sexual violence that has been going on there for years. " and amd gave in and rebranded it to this all so catchy name i always have to look up:
                              "2nd Generation Ultrathin Platform"

                              Comment


                              • #60
                                If i want to try out this new code i just must follow this guide?
                                http://wiki.x.org/wiki/radeonhd%3Aexperimental_3D

                                Comment

                                Working...
                                X