Page 12 of 15 FirstFirst ... 21011121314 ... LastLast
Results 111 to 120 of 143

Thread: Open-Source 2D, 3D For ATI Radeon HD 5000 Series GPUs

  1. #111
    Join Date
    Oct 2008
    Location
    Sweden
    Posts
    983

    Default

    Might be time to add an "Evergreen" column to http://www.x.org/wiki/RadeonProgram and start filling in the blanks?

  2. #112
    Join Date
    Nov 2008
    Location
    Germany
    Posts
    5,411

    Default

    Quote Originally Posted by whizse View Post
    Interesting! The r300g side of things is almost boringly fast and complete now, I'm tempted to order a new card...
    ironic nvidia users buy new hardware because nvidia force them by trop the cloused driver so newer xorg and kernel versions do not run

    and amd users drop hardware if all works fine in the driver and they need new stuff to play on ;-)

    come one R800 is so yesterday you need at minimum a fusion apu gpu or an 6870 to make sure you have something to do ;-)

    but next time the amd-OS driver team will be much faster because the difference on R900 are not so high because its just a refresh on the biggest parts.

    and you don't get so much time to 'play'

  3. #113
    Join Date
    Nov 2009
    Location
    Italy
    Posts
    918

    Default

    Quote Originally Posted by Qaridarium View Post
    but next time the amd-OS driver team will be much faster because the difference on R900 are not so high because its just a refresh on the biggest parts.
    They told the same thing with "evergreen" -.-

  4. #114
    Join Date
    Nov 2008
    Location
    Germany
    Posts
    5,411

    Default

    Quote Originally Posted by darkbasic View Post
    They told the same thing with "evergreen" -.-
    1 year of lag isn't so much time in an linux 'world'

    1 year later just means you get a better price for the same thing.

    but i think the next one will be faster.

  5. #115
    Join Date
    Nov 2008
    Posts
    766

    Default

    Quote Originally Posted by agd5f View Post
    geartrain looks fine here
    Just booted into the oss drivers again and re-checked, now it looks fine. Weird.
    Quote Originally Posted by agd5f View Post
    (other than the problems with the gear teeth on the back gear, but that's a bug in geartrain itself).
    I know, I fixed those Which is the only reason why I cared about geartrain anyway.
    Quote Originally Posted by agd5f View Post
    Make sure you 'make clean' before rebuilding.
    gentoo's git ebuilds are a bit more thorough than make clean.


    ioquake3: background-gfx in the menus are broken, but start working after playing a game. The game itself works. Mipmaps seem broken: screenshot.
    Still looks a lot better than these from 5 days ago.
    Strafing doesn't work as well as it used to when I last played it. Surely a driver bug.

    doom3: Went to the menu screen, <1 fps. Didn't enter a game because it's asking about my CD key which I don't have here (where'd my ~/.doom3 go?)

    ut: ~0.5fps, but the intro sequence (ingame-gfx) does render correctly.

    ut2k4: menu works as fast as it should. Starting a game results in
    ut2004-bin: radeon_texture.c:94: radeonFreeTexImageData: Assertion `!image->base.Data' failed.

    I re-tested dynpm. It obediently upped the frequencies to maximum when starting the first game, but didn't lower them again, not even on my desktop with virtually nothing running. Back to profile / low for now.

    I'm pretty sure there's still a nasty bug hidden somewhere, writing to parts of the video memory it shouldn't write to. I experienced it less frequently than before, but there still were small changes (red lines) in some pixmaps after running 3d apps. I wish I knew how to reproduce it or how to boil it down to a testcase :/


    I'm amazed by the amount of complex games that run. Just a few days ago glxgears could force my computer into a reboot, now I can frag stuff. Nice!

  6. #116
    Join Date
    Dec 2007
    Posts
    2,360

    Default

    I think the last two major issues for getting on par with r6xx/r7xx are fixing mipmaps and stencil buffers.

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

    Default

    Quote Originally Posted by darkbasic View Post
    They told the same thing with "evergreen" -.-
    Yep, and that's how it happened. Roughly ~31 months from launch to GL2 for 6xx, ~19 months for 7xx, <12 months for Evergreen... although it was arguably more like 8 months since work didn't really start until the end of 2009.

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

    Default

    ... and no, we're not going to make any schedule estimates for chips we haven't even launched yet

  9. #119
    Join Date
    Oct 2008
    Posts
    3,102

    Default

    Quote Originally Posted by bridgman View Post
    Yep, and that's how it happened. Roughly ~31 months from launch to GL2 for 6xx, ~19 months for 7xx, <12 months for Evergreen... although it was arguably more like 8 months since work didn't really start until the end of 2009.
    31, 19, 12. How does this series end?

    Clearly 7, 5, 2, 0.

    So, Bridgman has officially confirmed Fusion support coming next April!

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

    Default

    OK, so we need a word that describes the aggregate difficulty associated with supporting a new GPU family, including (among other things) degree of hardware change, completeness and accuracy of hardware documentation, trail of breadcrumbs left by driver teams (software documentation), other things going on at the same time... I guess PITA-ness is probably as close as we're going to get.

    Anyways, those numbers only work if you assume the next few generations of hardware follow an "equiPITA" curve

Tags for this Thread

Posting Permissions

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