Announcement

Collapse
No announcement yet.

AMD Pushes Out New R600/700 3D Code

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

  • AMD Pushes Out New R600/700 3D Code

    Phoronix: AMD Pushes Out New R600/700 3D Code

    In late December AMD had published open-source R600/700 3D code that also allowed for 2D and X-Video acceleration, but was not of use to end-users interested in full OpenGL acceleration. AMD had then released the R600/700 3D documentation a month later and then the R700 ISA documentation just a few weeks back. Today, however, AMD is finally pushing some workable code into a public code repository.

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

  • #2
    Hopefully this will extend to the rv870 when it is released. Looking forward to my next graphic card purchase, now that we have 3d(sorta) available in an open source driver for new cards.

    Comment


    • #3
      Woo yeah!! Nearly there now. I might actually try this stuff out but I'm confused about what's required to run it.

      Comment


      • #4
        This is awesome, thanks AMD!

        Comment


        • #5
          That is a synopsis of what is going on today within the open-source ATI world.
          Don't forget the power management thread

          And OpenCL

          Comment


          • #6
            Originally posted by sc3252 View Post
            Hopefully this will extend to the rv870 when it is released. Looking forward to my next graphic card purchase, now that we have 3d(sorta) available in an open source driver for new cards.
            Luckily, the R8xx still bases around the R6xx architecture, so it should be able to use a great part of this code.

            Comment


            • #7
              Originally posted by d2kx View Post
              Luckily, the R8xx still bases around the R6xx architecture, so it should be able to use a great part of this code.
              Bridgman shared in a post for some time ago, that the whole problem of releasing the 3D specs was the DRM (Digital Restrictions Management).

              For the R800 this was taken into account, so the 3D stuff and DRM was separated.

              So the R800 will maybe not (?) share much with R6xx and R7xx ?

              Comment


              • #8
                Originally posted by Louise View Post
                For the R800 this was taken into account, so the 3D stuff and DRM was separated.
                Let's wait to see if it has happened yet. I wouldn't be too surprised if this will begin with R9xx only. Designing a chip takes years.

                So the R800 will maybe not (?) share much with R6xx and R7xx ?
                I don't think that seperating DRM and 3D will have very strong differences in the code.

                Comment


                • #9
                  Originally posted by d2kx View Post
                  Let's wait to see if it has happened yet. I wouldn't be too surprised if this will begin with R9xx only. Designing a chip takes years.
                  I can't remember his exact quote, so you could be right, that it was for R900 based cards. But I really remember it as being for R800 based.

                  Originally posted by d2kx View Post
                  I don't think that seperating DRM and 3D will have very strong differences in the code.
                  At least for now, there isn't any information on R800.

                  What is the typical life cycle for ATi cards? 2years?

                  Comment


                  • #10
                    More like 3-4 years for a new generation. We're already hooked into future GPU development work so the delay from intro to open source driver support should be shorter than for previous generations when we were mostly playing "catch-up".

                    One of the big changes with 6xx was at least partially separating the programming model from the hardware implementation, so big changesa in the hardware have relatively less impact on the driver than in previous generations. 6xx and 7xx are very different hardware implementations but the programming interface is pretty similar. The downside was that it took a lot of work to get drivers running on the new programming model in the first place, but we're mostly past that now.

                    The discussion about "separating" was for DRM and UVD, shouldn't have any impact on 3D. I obviously can't comment on status.
                    Last edited by bridgman; 04-18-2009, 12:31 PM.

                    Comment


                    • #11
                      Originally posted by bridgman View Post
                      More like 3-4 years for a new generation. We're already hooked into future GPU development work so the delay from intro to open source driver support should be shorter than for previous generations when we were mostly playing "catch-up".
                      So the future is being made today

                      Originally posted by bridgman View Post
                      One of the big changes with 6xx was at least partially separating the programming model from the hardware implementation, so big changesa in the hardware have relatively less impact on the driver than in previous generations. 6xx and 7xx are very different hardware implementations but the programming interface is pretty similar. The downside was that it took a lot of work to get drivers running on the new programming model in the first place, but we're mostly past that now.
                      It is much appreciated nevertheless

                      Originally posted by bridgman View Post
                      The discussion about "separating" was for DRM and UVD, shouldn't have any impact on 3D. I obviously can't comment on status.
                      Reading Wikipedia it sounds like quite a complicated task!

                      http://en.wikipedia.org/wiki/Unified_Video_Decoder

                      Comment


                      • #12
                        Originally posted by Louise View Post
                        Bridgman shared in a post for some time ago, that the whole problem of releasing the 3D specs was the DRM (Digital Restrictions Management).

                        For the R800 this was taken into account, so the 3D stuff and DRM was separated.

                        So the R800 will maybe not (?) share much with R6xx and R7xx ?
                        No! 3D is free! UVD the mpeg2 und generaly the viedeo part has the DRM di-re-ma part in it!

                        so amd do not have bring the spec for the viedeo render part! becourse they can't

                        the R800 will Hopefulle chance this but AMD run's Out of money so i think amd can't chance this!

                        so i think... they bring DirectX11 by driver and microcode update to the rv740!

                        and the don't chance the UVD part in the R800--- but if they have more money again the will chance this in the future. --->R900
                        Last edited by Qaridarium; 04-18-2009, 08:22 PM.

                        Comment


                        • #13
                          Hi,

                          Do you know where the source code is published?
                          Is it in mesa repo? I found two branches, r6xx-r7xx-support and radeon-rewrite.

                          Is it in these?

                          Comment


                          • #14
                            The 3d code is in r6xx-r7xx-support. The radeon-rewrite branch is where airlied and others are adding support for running over a drm with memory manager and kernel modesetting (KMS/GEM/TTM).

                            There is a third branch, r6xx-rewrite, which is where we made a copy of radeon-rewrite and have started porting the 6xx/7xx 3d code into radeon-rewrite -- so the name is a hybrid of 6xx-7xx-support and radeon-rewrite

                            Comment


                            • #15
                              Originally posted by bridgman View Post
                              The 3d code is in r6xx-r7xx-support. The radeon-rewrite branch is where airlied and others are adding support for running over a drm with memory manager and kernel modesetting (KMS/GEM/TTM).

                              There is a third branch, r6xx-rewrite, which is where we made a copy of radeon-rewrite and have started porting the 6xx/7xx 3d code into radeon-rewrite -- so the name is a hybrid of 6xx-7xx-support and radeon-rewrite
                              So these are not different drivers then, just different branches of the same code base?

                              Comment

                              Working...
                              X