Announcement

Collapse
No announcement yet.

Initial R6xx/R7xx 3D Driver

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

  • nanonyme
    started a topic Initial R6xx/R7xx 3D Driver

    Initial R6xx/R7xx 3D Driver

    Since there's not an article about it yet on Phoronix, decided to link this up.
    http://www.botchco.com/agd5f/?p=43

  • nanonyme
    replied
    Right, managed to try it on 2.6.27. Works similar to the screenshots for a short time (read: several seconds) after which it locked X for me. When I tried to use magic sysrq to kill X, kernel hardlocked. Figures.
    I guess I'll just have to wait a bit still. ^^

    Leave a comment:


  • PuckPoltergeist
    replied
    I hade a little hopa that downgrading the kernel will fix my problem too, since I've had to patch the drm-code to work with the latest kernel.

    Leave a comment:


  • bridgman
    replied
    Hold on, you guys are talking about completely different things here.

    PuckPoltergeist, my earlier post applies to the problem you reported; there's probably something wrong in code which will get replaced over the next week or so, so we're not planning to troubleshoot the existing tree yet.

    Nanonyme, agd5f's post applies to you (re: problems getting the drm to run at all). I *think* the 6xx-rewrite mesa branch will use different code paths in the existing drm tree, so to some extent the same "wait until we get the code running in 6xx-rewrite" applies.

    Leave a comment:


  • PuckPoltergeist
    replied
    Originally posted by agd5f View Post
    The drm part might get changed a bit, but probably not much. My drm tree is known to work with 2.6.27 and 2.6.28, so if you want to play with this stuff use one of those kernels for now.
    Hm, I'm playing with git HEAD here (2.6.30-rc). Will give 2.6.28 a try.

    edit: same errors with 2.6.28.9
    Last edited by PuckPoltergeist; 04-29-2009, 04:00 PM.

    Leave a comment:


  • agd5f
    replied
    The drm part might get changed a bit, but probably not much. My drm tree is known to work with 2.6.27 and 2.6.28, so if you want to play with this stuff use one of those kernels for now.

    Leave a comment:


  • nanonyme
    replied
    Originally posted by bridgman View Post
    It's probably going to be a week or so before the devs get back to troubleshooting bugs. Right now the priority is getting the new 3D code running on the radeon-rewrite base, which involves different paths for the bottom part of the 3D driver and different paths in the DRM IIRC.

    The code where the problems are likely to be is the code that's going to be replaced in a week
    Maybe, maybe not. I'm having my problems solely with the DRM code. (I'm confident agd5f and folks will check compatibility issues soon. I was mostly trying to find out if my problems were due to Fedora modifications to the kernel or if 2.6.29 is simply too Different (tm))
    Edit: Oh, you meant the DRM part might get rewritten too?

    Leave a comment:


  • PuckPoltergeist
    replied
    Originally posted by bridgman View Post
    It's probably going to be a week or so before the devs get back to troubleshooting bugs. Right now the priority is getting the new 3D code running on the radeon-rewrite base, which involves different paths for the bottom part of the 3D driver and different paths in the DRM IIRC.

    The code where the problems are likely to be is the code that's going to be replaced in a week
    Ah ok, good to know. I will try it again then.

    Leave a comment:


  • bridgman
    replied
    It's probably going to be a week or so before the devs get back to troubleshooting bugs. Right now the priority is getting the new 3D code running on the radeon-rewrite base, which involves different paths for the bottom part of the 3D driver and different paths in the DRM IIRC.

    The code where the problems are likely to be is the code that's going to be replaced in a week

    Leave a comment:


  • PuckPoltergeist
    replied
    Hm, glxgears won't work here. Perhaps again AGP related?

    The output:
    Code:
    [email protected] ~ $ glxgears
    [r600]  Mappings:
            Registers                         cpu 0x7f13d09a6000   size 0x00010000   handle 0xff3f0000
            Status                            cpu 0x7f13d09a5000   size 0x00001000   handle 0xf0101000
            GART           gpu 0x00f0000000
            DRM buffers    gpu 0x00f0102000   cpu 0x7f13bbc7a000   size 0x00200000
            GART Textures  gpu 0x00f0302000   cpu 0x7f13bbe7a000   size 0x01c80000   handle 0xf0302000
            Framebuffer    gpu 0x00d0000000   cpu 0x7f13bdafa000   size 0x10000000
            Front Target   gpu 0x00d0000000   cpu 0x7f13bdafa000   size 0x00b7c000   pitch 0x0700
            Back  Target   gpu 0x00d0b84000   cpu 0x7f13be67e000   size 0x00b7c000   pitch 0x0700
            Depth Target   gpu 0x00d1700000   cpu 0x7f13bf1fa000   size 0x00b7c000   pitch 0x0700
    
    [r600] r600MakeCurrent   (r600_context.c:413)
    [r600]    Context 0x123a230 Draw 0x1239510 Read 0x1239510
    [r600] r600MemAlloc   (r600_mem.c:289)   allocated 1 at age 0
    [r600] r600MemFree   (r600_mem.c:328)   freed 1 at age 0
    [r600] r600CopyBuffer   (r600_screen.c:479)
    [r600]    ClipRect 5:25-305:325
    [r600] r600CopyBuffer   (r600_screen.c:479)
    [r600]    ClipRect 5:25-305:325
    [r600] r600CopyBuffer   (r600_screen.c:479)
    [r600]    ClipRect 5:25-305:325
    [r600] r600CopyBuffer   (r600_screen.c:479)
    [r600]    ClipRect 5:25-305:325
    [r600] r600CopyBuffer   (r600_screen.c:479)
    [r600]    ClipRect 5:25-305:325
    [r600] r600CopyBuffer   (r600_screen.c:479)
    [r600]    ClipRect 5:25-305:325
    [r600] r600CopyBuffer   (r600_screen.c:479)
    [r600]    ClipRect 5:25-305:325
    [r600] r600CopyBuffer   (r600_screen.c:479)
    [r600]    ClipRect 5:25-305:325
    [r600] r600CopyBuffer   (r600_screen.c:479)
    [r600]    ClipRect 5:25-305:325
    [r600] r600MemAlloc   (r600_mem.c:289)   allocated 1 at age 0
    [r600] r600MemFree   (r600_mem.c:328)   freed 1 at age 0
    glxgears: r600_mem.c:297: r600MemFree: Assertion `id <= context->memManager->u_last' failed.
    Abgebrochen
    dmesg:
    Code:
    agpgart-amd64 0000:00:00.0: AGP 3.0 bridge
    agpgart: X tried to set rate=x12. Setting to AGP3 x8 mode.
    agpgart-amd64 0000:00:00.0: putting AGP V3 device into 8x mode
    radeon 0000:01:00.0: putting AGP V3 device into 8x mode
    [drm] Setting GART location based on new memory map
    [drm] Loading RV635 CP Microcode
    [drm] Loading RV635 PFP Microcode
    [drm] Resetting GPU
    [drm] writeback test succeeded in 2 usecs
    [drm:r600_cs_packet3] *ERROR* bad tex base 0x0000000000000000
    [drm:r600_cs_packet3] *ERROR* fb 0x20000000, 0xd0000000 - 0xefffffff
    [drm:r600_cs_packet3] *ERROR* gart 0x02000000, 0xf0000000 - 0xf1ffffff
    [drm:r600_cs_packet3] *ERROR* bad SET_RESOURCE
    [drm:r600_cs_packet3] *ERROR* bad tex base 0x0000000000000000
    [drm:r600_cs_packet3] *ERROR* fb 0x20000000, 0xd0000000 - 0xefffffff
    [drm:r600_cs_packet3] *ERROR* gart 0x02000000, 0xf0000000 - 0xf1ffffff
    [drm:r600_cs_packet3] *ERROR* bad SET_RESOURCE
    [drm:r600_cs_packet3] *ERROR* bad tex base 0x0000000000000000
    [drm:r600_cs_packet3] *ERROR* fb 0x20000000, 0xd0000000 - 0xefffffff
    [drm:r600_cs_packet3] *ERROR* gart 0x02000000, 0xf0000000 - 0xf1ffffff
    [drm:r600_cs_packet3] *ERROR* bad SET_RESOURCE
    [drm:r600_cs_packet3] *ERROR* bad tex base 0x0000000000000000
    [drm:r600_cs_packet3] *ERROR* fb 0x20000000, 0xd0000000 - 0xefffffff
    [drm:r600_cs_packet3] *ERROR* gart 0x02000000, 0xf0000000 - 0xf1ffffff
    [drm:r600_cs_packet3] *ERROR* bad SET_RESOURCE
    /var/log/Xorg.0.log doesn't show something related to this failure

    Leave a comment:

Working...
X