Announcement

Collapse
No announcement yet.

AMD Pushes Out New R600/700 3D Code

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

  • #31
    Anyone success with the latest commit? I had to disable gallium to get it to build. But running glxinfo now gives me:

    Code:
    Fatal error in __driConfigOptions line 284, column 0: illegal default value: DRI_CONF_FP_OPTIMIZATION_SPEED
    Aborted

    Comment


    • #32
      Which branch did you build ? Richard's latest push in 6xx-rewrite was just work-in-progress, still a bit more to do before it runs.

      We're trying to keep the ported code visible even if it's not actually making triangles yet.

      Comment


      • #33
        Yeah I'm using r6xx-rewrite now. I guess I have to wait a little longer...

        Comment


        • #34
          Originally posted by bridgman View Post
          Which branch did you build ? Richard's latest push in 6xx-rewrite was just work-in-progress, still a bit more to do before it runs.

          We're trying to keep the ported code visible even if it's not actually making triangles yet.
          No sweat imo, it was already nice to see the rewrite effort going somewhere.

          Comment


          • #35
            RE: Radeonhd
            Originally posted by nanonyme View Post
            Now now, of course people should care. It's just not an imminent matter and can be safely ignored for the time being. (maybe even for years)
            One good thing about radeonhd is that it allows output of sound over hdmi. Radeon-ati doesn't do that, or at least I haven't easily figured out how to make it work. As catalyst is not working with the 2.6.29 kernel (without patching), radeonhd is an option unless 3D acceleration is required.

            Comment


            • #36
              Originally posted by forum1793 View Post
              RE: Radeonhd


              One good thing about radeonhd is that it allows output of sound over hdmi. Radeon-ati doesn't do that, or at least I haven't easily figured out how to make it work. As catalyst is not working with the 2.6.29 kernel (without patching), radeonhd is an option unless 3D acceleration is required.
              It only doesn't do that because no one has yet had spare time to port the functionality over afaik. Iirc someone said it wouldn't be a big task but quite frankly I understand if it atm isn't a priority. I'm confident it will eventually happen. (in the meantime your argument is valid)

              Comment


              • #37
                Just a note so I get this written down somewhere: anyone else getting their num lock, caps lock and scroll lock lights blinked randomly on and off with the r6xx-r7xx-3d DRM? Happens for me, I only get rid of it by rebooting.

                Comment


                • #38
                  Originally posted by bridgman View Post
                  Which branch did you build ? Richard's latest push in 6xx-rewrite was just work-in-progress, still a bit more to do before it runs.

                  We're trying to keep the ported code visible even if it's not actually making triangles yet.
                  Also that same macro seems to be defined in r300_fragprog.h but seems to be missing from r700_fragprog.h altogether. (Or am I missing something?)

                  Comment


                  • #39
                    Originally posted by monraaf View Post
                    Anyone success with the latest commit? I had to disable gallium to get it to build. But running glxinfo now gives me:

                    Code:
                    Fatal error in __driConfigOptions line 284, column 0: illegal default value: DRI_CONF_FP_OPTIMIZATION_SPEED
                    Aborted
                    Having played around with things a bit last night, I suspect you did the same mistake I did. Are you sure you told it --with-dri-drivers=radeon,r600? Since when I did that, I ran into compiling problems that I could only solve by combining some parts from agd5f's DRM with modesetting-gem libdrm. (I don't describe here exactly what I did nor do I recommend it because the end result was a lockup in starting X)
                    Edit: As in, I found out that not only should it not work, it also should not compile.
                    Last edited by nanonyme; 05-18-2009, 07:28 AM.

                    Comment


                    • #40
                      Unfortunately can't edit my previous message anymore: the mixup with libdrm was my own fault. Solved in a fresh installation.

                      Comment


                      • #41
                        Yeah, I got glxinfo running:

                        Code:
                        OpenGL vendor string: Advanced Micro Devices, Inc.
                        OpenGL renderer string: Mesa DRI R600 20090101 x86/MMX+/3DNow!+/SSE2 TCL
                        OpenGL version string: 1.4 Mesa 7.5-devel
                        For some reason the preprocessor didn't replace DRI_CONF_FP_OPTIMIZATION_SPEED with what it's defined to be, so I just replaced it myself with 0.
                        Also I had to add my chip id to radeon_set_screen_flags(). Note to AMD: 0x9610 is also an RS780!

                        glxgears now locks up the X server after printing some numbers related to pixel and vertex shaders .

                        Comment


                        • #42
                          Richard pushed a couple of updates earlier today. The "clear" code is still broken but that's next on his list.

                          Comment


                          • #43
                            Originally posted by bridgman View Post
                            Richard pushed a couple of updates earlier today.
                            Yeah, I noticed. I have subscribed to the git rss feed The headline "redbook hello can run" grabbed my attention. Unfortunately just like glxgears it locks up the X server here.

                            Comment


                            • #44
                              Hmm... I know it still needs work but I don't think it should be locking up the X server. I have pinged the devs for comment...

                              EDIT - Richard said that glxgears *does* hang the system (he's working on that) but he wouldn't expect the Redbook "Hello" program to do that. There is some corruption in "Hello" because the clear code is stubbed out though.

                              Just checking, are you using the latest drm from the r6xx-r7xx-3d branch of ~agd5f/drm ? Last change was about 6 days ago but Bad Things will happen with older code.

                              EDIT - Richard also mentioned that he is using Option "AccelMethod" "None" for testing right now, in case that helps.
                              Last edited by bridgman; 05-19-2009, 04:12 PM.

                              Comment


                              • #45
                                I do have the latest drm from agd5f's 3d branch installed. AccelMethod none doesn't do anything here, I still get normal 2D acceleration and Xv and a lock up with the redbook hello program. Maybe Richard is using radeonHD?

                                Instead of immediately rebooting after a lock up, this time I waited some time hoping that the server would resume normal operation after a while
                                It didn't...but if it's of any use my dmesg got spammed with a lot of:

                                Code:
                                [drm] wait for fifo failed status : 0xA02034AC 0x00000003
                                Edit: RadeonHD doesn't seem to work with agd5f's drm. No acceleration at all and Mesa Software Rasterizer.
                                Last edited by monraaf; 05-20-2009, 01:08 AM.

                                Comment

                                Working...
                                X