Linked by Thom Holwerda on Wed 9th Sep 2009 22:29 UTC, submitted by lemur2
Permalink for comment 383342
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2007-02-17
While the 3D support was being developed, I believe that initially they were using memcopy (software) function. One of the "todo" tasks was to write proper memory management and to use DMA.
http://www.phoronix.com/scan.php?page=news_item&px=NzQyNg
I'd imagine that that has been fixed by now.
Check near the end of this thread:
http://www.phoronix.com/forums/showthread.php?t=18959
Now the only problem for me is the lack of suspend. Other than that it works well: stable and fast 2D and 3D.
The 3D code is mostly common between DRI1 and DRI2 -- this is the upside from porting the 3D driver over to the radeon-rewrite code base a few months ago. Doing that port delayed the 3D driver by a couple of months, but it meant that the move to KMS and DRI2 would be simplified.
That said, I am *still* surprised how well it all came together.
Edited 2009-09-11 00:08 UTC