Page 1 of 20 12311 ... LastLast
Results 1 to 10 of 199

Thread: AMD Releases Open-Source R600/700 3D Code

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,816

    Default AMD Releases Open-Source R600/700 3D Code

    Phoronix: AMD Releases Open-Source R600/700 3D Code

    Since earlier this year we have been waiting for AMD to release documentation and/or code on the ATI R600 series concerning 3D acceleration so that the open-source Linux drivers can begin to support the newer ATI graphics processors. It has taken longer than expected for AMD to complete and release this information, but it's now available. AMD has released the fundamental Linux code needed to begin fostering the development of an open-source R600 3D driver. Furthermore, this code also concerns the latest R700 series of graphics processors! The microcode for the newest GPUs has also been released.

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

  2. #2
    Join Date
    Mar 2008
    Location
    Osnabrück, Germany
    Posts
    79

    Default

    Well, THAT's a late christmas present!
    Thx to everyone involved in this!

  3. #3
    Join Date
    Aug 2007
    Posts
    6,631

    Default

    I just don't get why radeonhd will get it faster than radeon when agd5f works for ATI and on the radeon driver?

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

    Default

    Quote Originally Posted by Kano View Post
    I just don't get why radeonhd will get it faster than radeon when agd5f works for ATI and on the radeon driver?
    Alex has been working on acceleration code in radeonhd for quite a while. We are trying to keep the acceleration code relatively common between the two drivers anyways.

  5. #5
    Join Date
    Mar 2008
    Location
    Osnabrück, Germany
    Posts
    79

    Default

    Quote Originally Posted by bridgman View Post
    ...We are trying to keep the acceleration code relatively common between the two drivers anyways.
    Well that leads to the question about the reason for two drivers() but don't listen to me, that has been discussed several times here let's not do it again.

  6. #6
    Join Date
    Jun 2008
    Location
    Groningen, The Netherlands
    Posts
    42

    Default

    Quote Originally Posted by Kano View Post
    I just don't get why radeonhd will get it faster than radeon when agd5f works for ATI and on the radeon driver?
    I'm glad they did, this way at least I can enjoy both perfect HDMI audio AND 3D!

    Where do I send the champagne?
    Last edited by StefanHamminga; 12-29-2008 at 05:13 PM.

  7. #7
    Join Date
    Dec 2008
    Posts
    2

    Default

    Aaaaaah now that's some awesome news ... thank you very much to everyone involved !

    /me hoping to soon be able to drop those barely working, crashy buggy proprietary drivers :-)

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

    Default

    let's see... Nuremberg is closest to you, send the champagne to SuSE

  9. #9

    Default

    Very nice news!

    I have a question, however. What about the source of the DRM microcode? Without that the driver can't be considered fully open source.

    Note that Intel is shipping full source for their assembler code (source in .g4a files, compiled microcode in .g4b files), making it a fully open source driver:
    http://cgit.freedesktop.org/xorg/dri...intel/tree/src

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

    Default

    Quote Originally Posted by oibaf View Post
    I have a question, however. What about the source of the DRM microcode? Without that the driver can't be considered fully open source.
    I didn't think the Intel GPUs used loadable microcode, but I could be wrong. All of the .g4a and .g4b files I saw looked like driver code (shader code called by the driver, to be precise). Anyways, the use of microcode blobs seems to be generally accepted, although there are occasional pushes to have them loaded from user space so the kernel guys don't have to feel dirty.

    EDIT - geez, Intel shader code is nearly as hard to read as ours

    re: ongoing 5xx love, I think the plan is to implement KMS/MM all the way back to R100 and Gallium3D/GL2 as far back as R300, so no worries.
    Last edited by bridgman; 12-29-2008 at 05:15 PM.

Posting Permissions

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