Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 33

Thread: Any timeline on RadeonHD 3D/Xv support?

  1. #11
    Join Date
    Sep 2007
    Posts
    29

    Default

    Quote Originally Posted by bridgman View Post
    The changes are in the mesa/drm master but I don't think drm is included in the mesa release.

    I believe the actual mesa/mesa R5xx 3D support is still off in a branch, so it would not be in 7.03.
    Right, for git mesa master or 7.0.3, R5xx 3D is not supported, but we can use Xv just fine.

  2. #12
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,385

    Default

    Yep. Xv only uses code from the X driver and drm, not from mesa.

  3. #13
    Join Date
    Feb 2007
    Posts
    22

    Default

    Is 3D supposed to work with Radeon on R500? I have an x1400. I only get software libGL support. I have the latest radeon from git as of today, and mesa + drm from two days ago. Here's some diagnostics:

    elenius@elenius-laptop:~$ dmesg | grep drm
    [ 45.782753] [drm] Initialized drm 1.1.0 20060810
    [ 45.857535] [drm] Initialized radeon 1.28.0 20060524 on minor 0
    [ 47.478703] [drm] Setting GART location based on new memory map
    [ 47.480072] [drm] Loading R500 Microcode
    [ 47.480143] [drm] writeback test succeeded in 2 usecs
    elenius@elenius-laptop:~$ grep -i "Direct rendering" /var/log/Xorg.0.log
    (II) RADEON(0): Direct rendering enabled
    elenius@elenius-laptop:~$ export LIBGL_DEBUG=verbose
    elenius@elenius-laptop:~$ glxinfo
    name of display: :0.0
    libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0)
    libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/r300_dri.so
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 4, (OK)
    drmOpenByBusid: Searching for BusID pci:0000:01:00.0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 4, (OK)
    drmOpenByBusid: drmOpenMinor returns 4
    drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
    unknown chip id 0x7145, can't guess.
    libGL error: InitDriver failed
    libGL error: reverting to (slow) indirect rendering

  4. #14
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,385

    Default

    Git masters for radeon and drm are good for R5xx 3D, but you still need to get mesa/mesa from airlied's R500 branch :

    http://cgit.freedesktop.org/~airlied...og/?h=r500test

    You might still have to add your chip ID in order to be recognized -- Dave only put a couple of R5xx IDs in the code himself.

  5. #15
    Join Date
    May 2007
    Posts
    352

    Default

    How does one go about checking out that mesa version? I ran 'git clone git://cgit.freedesktop.org/~airlied/mesa', but git-log in the newly created mesa directory doesn't show any updates since April of 2007, so I'm assuming I have to checkout a particular branch, correct?

    Adam

  6. #16
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,385

    Default

    Yes, I believe you need the "r500test" branch.

  7. #17
    Join Date
    May 2007
    Posts
    352

    Default

    Maybe I just don't know git well enough... I thought 'git-checkout r500test' would be enough, but that gives me:

    error: pathspec 'r500test' did not match any file(s) known to git.
    Did you forget to 'git add'?

  8. #18
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,385

    Default

    I certainly don't know git well enough either... yet.

    Does the following (Michael's IRC advice to someone else trying to do the same) help ?

    "michaellarabel: git-clone the airlied branch and then change directories to drm or mesa and then do: git-checkout -b r500test origin/r500test"
    Last edited by bridgman; 04-13-2008 at 11:15 AM.

  9. #19
    Join Date
    May 2007
    Posts
    352

    Default

    That did it :-) Thanks! I owe you a beer next time you're in southern NJ.

    Adam

  10. #20
    Join Date
    May 2007
    Posts
    352

    Default

    Heh, I may have to wait a bit to try again. The mesa driver builds, but GL apps fail with:

    libGL warning: 3D driver returned no fbconfigs.
    libGL warning: 3D driver returned no fbconfigs.
    libGL error: InitDriver failed
    libGL error: reverting to (slow) indirect rendering
    glxgears: Error: couldn't get an RGB, Double-buffered visual.

    So I figured that I might need to build an x server from around the same time as the last commit to the r500 branch (March 21st), so I reset to a commit from the 20th, but that fails to build :-)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •