Announcement

Collapse
No announcement yet.

ATI R600/700 OSS 3D Driver Reaches Gears Milestone

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

  • I'm not part of any team but 2.6.31 will only give you 2D accel on r600/r700. For the rest you're looking for 2.6.32 or greater or agd5f's DRM branch.

    Comment


    • My dmesg

      Code:
       
      [    7.179317] [drm] Initialized drm 1.1.0 20060810
      [    7.250930] radeon 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
      [    7.250986] radeon 0000:04:00.0: setting latency timer to 64
      [    7.251146] [drm] Initialized radeon 1.29.0 20080613 on minor 0
      [   21.784953] [drm] Setting GART location based on new memory map
      [   21.800115] [drm] Loading RV730/RV740 PFP Microcode
      [   21.800143] [drm] Loading RV730/RV740 CP Microcode
      [   21.815206] [drm] Resetting GPU
      [   21.815261] [drm] writeback test succeeded in 1 usecs
      My Xorg.log

      Code:
      (II) "dri" will be loaded. This was enabled by default and also specified in the config file.
      (II) LoadModule: "dri"
      
      (II) Loading /usr/lib/xorg/modules//extensions/libdri.so
      (II) Module dri: vendor="X.Org Foundation"
              compiled for 1.5.2, module version = 1.0.0
              ABI class: X.Org Server Extension, version 1.1
      (II) Loading /opt/xorg/lib/xorg/modules//drivers/radeon_drv.so
      (II) Module radeon: vendor="X.Org Foundation"
              compiled for 1.5.2, module version = 6.12.2
              Module class: X.Org Video Driver
              ABI class: X.Org Video Driver, version 4.1
      (II) RADEON(0): TOTO SAYS 00000000cffe0000
      (II) RADEON(0): MMIO registers at 0x00000000cffe0000: size 64KB
      (II) RADEON(0): PCI bus 4 card 0 func 0
      (**) RADEON(0): Depth 24, (--) framebuffer bpp 32
      (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
      (==) RADEON(0): Default visual is TrueColor
      (**) RADEON(0): Option "AccelMethod" "exa"
      (**) RADEON(0): Option "DRI" "on"
      drmOpenDevice: node name is /dev/dri/card0
      drmOpenDevice: open result is 10, (OK)
      drmOpenByBusid: Searching for BusID pci:0000:04:00.0
      drmOpenDevice: node name is /dev/dri/card0
      drmOpenDevice: open result is 10, (OK)
      drmOpenByBusid: drmOpenMinor returns 10
      drmOpenByBusid: drmGetBusid reports pci:0000:04:00.0
      (II) RADEON(0): [dri] Found DRI library version 1.3.0 and kernel module version 1.29.0
      (==) RADEON(0): Page Flipping disabled on r5xx and newer chips.
      My xorg.conf

      Code:
      Section "Device"
        BoardName    "ATI Radeon Graphics Processor (RV730 9490)"
        Driver       "radeon"
        Identifier   "Device[0]"
        Option       "monitor-DVI-I_2/digital" "Monitor[0]"
        VendorName   "ATI"
        Option      "AccelMethod" "exa" # default shadowfb
        Option      "DRI" "on"
      Option "BusType" "PCIE"
      EndSection
      Section "DRI"
          Group      "video"
          Mode       0660
      EndSection

      Comment


      • Originally posted by rvdboom View Post
        I have a quick question for the AMD team : what level of support is brought by the incoming 2.6.31 kernel for r600 and r700?
        I seem to remember that KMS was for r500 and lower, but there seem to be some code for r600 in the I have a quick question for the AMD team : what level of support is brought by the incoming 2.6.31 kernel for r600 and r700?
        I seem to remember that KMS was for r500 and lower, but there seems to be some code for r600 in the /drivers/gpu/drm/radeon dir in the kernel tree.
        Is that supposed to be enough to get 3D with r600-r700 devices or does one still need to use the specific r600-r700 kernel modules branch to make it work?
        Do you mind if I answer? I'm not part of AMD team.

        .31 gives you 2D for R6xx/R7xx and somehow experimental (staging) KMS for r1xx-r5xx. New features usually can be pushed in merging window only, so don't expect new features to be added between rc1 and final.

        On the other hand we will see merge window for .32 soon. So expect many new features hitting mainline and slowly going to .32 stable release.

        Comment


        • With the latest git, OpenGL compositing in KDE works longer than before, but when I tried enabling the desktop cube, the system hung, and I could only move the mouse around (sluggishly).

          Comment


          • 2.6.30 added EXA and Xv support for 6xx/7xx

            2.6.31 added KMS/GEM/TTM support for r1xx-r5xx (staging only)

            2.6.32 will hopefully add KMS/GEM/TTM support for 6xx/7xx (staging only) and 3D support for 6xx/7xx (normal, not staging). I think the intent is for KMS/GEM/TTM on r1xx-r5xx to move out of staging but I'm not sure about that.

            Comment


            • Is the plan to freeze the kernel drm once it moves into the mainline kernel? Or will we need bleeding edge kernels to follow the 3D development?

              Comment


              • I think the intention is once the merge to 2.6.32 happens you should not need out-of-tree kernel code - at least for DRI1.

                Comment


                • Originally posted by bridgman View Post
                  2.6.30 added EXA and Xv support for 6xx/7xx

                  2.6.31 added KMS/GEM/TTM support for r1xx-r5xx (staging only)

                  2.6.32 will hopefully add KMS/GEM/TTM support for 6xx/7xx (staging only) and 3D support for 6xx/7xx (normal, not staging). I think the intent is for KMS/GEM/TTM on r1xx-r5xx to move out of staging but I'm not sure about that.
                  To clarify this a little for the non-coder-genius people out there, myself included , for those with r7xx or higher cards using the radeon/hd driver, come 2.6.32, we'll have accelerated 2d for kwin (i.e. wobbly windows in kde etc etc), but games will still remain un-accelerated?

                  Comment


                  • Originally posted by Maarte View Post
                    To clarify this a little for the non-coder-genius people out there, myself included , for those with r7xx or higher cards using the radeon/hd driver, come 2.6.32, we'll have accelerated 2d for kwin (i.e. wobbly windows in kde etc etc), but games will still remain un-accelerated?
                    I don't think so : 3D support without KMS still means 3D support, so accelerated 3D in games, just as most cards ATI currently accelerate 3D.

                    By the way, I switched over to KMS/TTM/GEM using the 2.6.31rc8 and latest git on a laptop with XP200M chip (I think it's something like RS480 or something) and it's quite stable already. Can't I see much difference with the situation before that, but it's surely stable and if that means getting better things in the future, it surely is a good job done! I guess the next step is to check Gallium3D there. :-)

                    Comment


                    • That's great news! Thanks for the heads-up. Amazing to see the ATi open drivers progress over this last year. Excellent work.

                      Comment


                      • Originally posted by Maarte View Post
                        we'll have accelerated 2d for kwin (i.e. wobbly windows in kde etc etc)
                        With 2D acceleration (XRender), you can use compositing with KWin. Unfortunately, not all fancy desktop effects work with the XRender backend. Desktop cube, for example, needs OpenGL, and wobbly windows too.

                        But transparency, fading, moving windows around, expose, and many other cool effects work, and are fast and stable in KWin. You don't need to wait for anything, you can already get this with the .31 kernel and recent radeon/radeonhd driver.

                        For some of the remaining effects, you'll have to wait for 3d. The kernel part of this should hopefully get merged into the .32 kernel. But that doesn't mean that everything will work perfectly, as there are other parts needed for 3d which are developed outside of the kernel (Mesa). The KWin with OpenGL backend still doesn't really work for me.
                        Last edited by pingufunkybeat; 09-05-2009, 01:57 PM.

                        Comment


                        • just a question

                          is the infrastructure needed (in the kernel) for Gallium ready??

                          and if not in which kernel version is going to be ready??

                          thanks

                          Comment


                          • Originally posted by 89c51 View Post
                            just a question

                            is the infrastructure needed (in the kernel) for Gallium ready??

                            and if not in which kernel version is going to be ready??

                            thanks
                            gallium uses the same ioctls as the kms-enabled ddx and 3d drivers. 2.6.31 has everything you need for r3xx-r5xx, and 2.6.32 will for r6xx/r7xx. However there is not yet an r600 gallium driver.

                            Comment


                            • Originally posted by FarJumper View Post
                              It looks that libgl1-mesa-dri package (libgl1-mesa-dri 7.6.0+git20090902.dc9de806-0ubuntu0tormod) doesn't have r600 module. Only r200 and r300 are exist.
                              Oops, I forgot to add r600 to that package. I uploaded a new right now.

                              Comment


                              • I for the first time tried the R6xx/R7xx 3D stuff on Kubuntu 9.10 with my AMD Radeon HD 4850 today. The composite performance (KWin desktop effects) is better than fglrx + the 1-2s freezes when maximizing windows/etc. are gone :P It isn't fully stable though (of course).

                                Comment

                                Working...
                                X