Page 1 of 41 12311 ... LastLast
Results 1 to 10 of 406

Thread: ATI R600/700 OSS 3D Driver Reaches Gears Milestone

  1. #1
    Join Date
    Jan 2007
    Posts
    15,400

    Default ATI R600/700 OSS 3D Driver Reaches Gears Milestone

    Phoronix: ATI R600/700 OSS 3D Driver Reaches Gears Milestone

    Months after AMD released documentation, programming guides, and sample code for the ATI R600 (Radeon HD 2000/3000) and R700 (Radeon HD 4000) series, glxgears is finally running atop these newest ATI graphics processors with proper GPU acceleration. Three AMD employees have been working on this R600/700 3D support in the DDX, DRM, and Mesa, and now they finally have glxgears running atop their 3D driver that is now based off of the radeon-rewrite driver. There's still a lot of work to be accomplished when it comes to usable open-source 3D support with the ATI R600/700 GPUs, but this is an important step. More on this milestone is shared on Alex Deucher's blog...

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

  2. #2
    Join Date
    Apr 2008
    Location
    A Coruńa (Spain)
    Posts
    100

    Default

    Good. I'd rather have KMS and suspend working with my HD3850, but it's nice seeing things are improving fast.

  3. #3
    Join Date
    Apr 2009
    Posts
    565

    Default

    Fantastic, anyone knows when will the Mesa and DRM work be merged into there main branches?

    Thanks in advance!

  4. #4

    Default

    Hi

    Following the steps on the xorg wiki (http://www.x.org/wiki/radeonhd%3Aexperimental_3D) is all joyjoy until building mesa.

    In file included from radeon_bocs_wrapper.h:24,
    from radeon_common_context.h:19,
    from radeon_common.h:5,
    from radeon_screen.c:50:
    /usr/include/drm/radeon_cs.h: In function ‘radeon_cs_set_limit’:
    /usr/include/drm/radeon_cs.h:185: error: ‘RADEON_GEM_DOMAIN_VRAM’ undeclared (first use in this function)
    /usr/include/drm/radeon_cs.h:185: error: (Each undeclared identifier is reported only once
    /usr/include/drm/radeon_cs.h:185: error: for each function it appears in.)
    radeon_screen.c: In function ‘radeonGetParam’:
    radeon_screen.c:257: error: variable ‘info’ has initializer but incomplete type
    radeon_screen.c:257: warning: excess elements in struct initializer
    radeon_screen.c:257: warning: (near initialization for ‘info’)
    radeon_screen.c:257: error: storage size of ‘info’ isn’t known
    radeon_screen.c:257: warning: unused variable ‘info’

    Can anyone help me with this?


    $ uname -r -> 2.6.29.4-167.fc11.x86_64

  5. #5
    Join Date
    Jul 2008
    Posts
    77

    Default

    Congrats, guys!

    This will make choosing an R600/700 card over an Nvidia card easier for me when it comes time for me to upgrade my desktop PC.

  6. #6
    Join Date
    May 2008
    Posts
    598

    Default

    So it was champagne corks I heard earlier today

    For good reason too

    I think 15 FPS is very impressive for the very first build that works. I'd anything that is measured in FPS and not Frames Per Day, is impressive

    So where will AMD go from here? Fix bugs, or leave this to others, and start on other features?

    What a day! This is just too good to be true!

  7. #7
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,542

    Default

    All the devs noticed that the sun seemed to shine a bit more brightly today

    For the short term, I guess the tasks are :

    (a) continue to fix bugs,
    (b) get back to 1500fps from 15fps by accelerating the back-to-front buffer copy,
    (c) get the mesa code ready to merge into master

    The driver actually draws decently fast, it's just the buffer copy that slows everything down. The GPU can copy VRAM-to-VRAM at 2,000 MB/s or better, but the CPU can only copy at around 5 MB/s when it has to read from uncached VRAM. The CPU is probably reading one 32-bit word at a time, and taking maybe 800nS to go out to the GPU over PCIE, have the GPU read a word from VRAM, and return the data to the CPU. The glxgears window is ~300x300 pixels, or 360K bytes - 5MB/sec over 360KB/frame gives about 15 fps.

    Running fullscreen (say 1680x1050) the copy really does start to give us "Frames per Day" performance
    Last edited by bridgman; 07-15-2009 at 02:55 PM.

  8. #8
    Join Date
    Feb 2009
    Location
    France
    Posts
    309

    Default

    Nice! I just bought an HD4770, should be great!
    But I think I'll stick to catalyst, just to see how good it is to have decent performances (compared to an Xpress 200M).

    I suppose this will be merged in the 2.6.32, right?

  9. #9
    Join Date
    Sep 2008
    Posts
    113

    Default

    It's nice to see some actual improvement on Ati's side. I might finally get around to getting a new computer if this keeps improving. (I will never choose Nvidia for making faulty gpu's and blaming it on others)

    I remember when I was in high school, I had a desktop with an Ati 9600 (actually, I still have that box), and fglrx never worked. My brother and I joked that the card wouldn't actually run well under linux until we had children, and it looks like we might have been wrong. I'm going into a university soon, he's almosts done, and we might get functional Ati drivers before our careers start!

    Well, good job Ati at exceeding our expectations.

  10. #10
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,542

    Default

    FYI what I"m seeing right now is gears running properly on rv770 and mostly drawing black on an rv620 although dragging the window around makes the gears appear intermittently. Based on limited testing it is probably safe to say "seems to work on 7xx, colours aren't right on 6xx yet".

    The same applies to a number of other tests, eg the redbook demos.

Posting Permissions

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