| 1 |
Rafael Fernández López schreef: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I've read something somewhere that have amazed me... Is X.org |
| 5 |
> developing new ATI drivers, better far from ATI.com ? |
| 6 |
|
| 7 |
Yes and no... I think what you're talking about is most likely the open |
| 8 |
source r300 drivers (similar in effect to the open source 'radeon' |
| 9 |
kernel drivers that are available for the 9500 and below). |
| 10 |
|
| 11 |
More information can be found on these drivers here: |
| 12 |
|
| 13 |
http://r300.sourceforge.net/R300.php |
| 14 |
|
| 15 |
As far as I know, although the r300 project's code is available to X.org |
| 16 |
(and in fact has been accepted into the CVS tree), the project itself is not |
| 17 |
associated with, or rather is separate from, the X.org project itself. |
| 18 |
|
| 19 |
> |
| 20 |
> If that's affirmative... We will be able to use Damage extension (and |
| 21 |
> Composite extension) with ati rendering ? |
| 22 |
|
| 23 |
No idea, since I don't know what the Damage extension is/does, and afaik |
| 24 |
the Composite extension is not yet complete or stable, so it doesn't |
| 25 |
'matter' whether it works atm-- ATI themselves don't want to 'waste' |
| 26 |
resources on supporting Composite until it's done, so I can't imagine |
| 27 |
that the Open Source project is going to focus on it yet either (having |
| 28 |
less resources and information than ATI themselves). |
| 29 |
|
| 30 |
> |
| 31 |
> And when is X.org going to be able on portage ? |
| 32 |
|
| 33 |
As noted on the r300 site, 'The latest source code is available directly |
| 34 |
from Xorg, Mesa and DRM CVS trees.' |
| 35 |
|
| 36 |
I would assume that 'the Xorg, Mesa and DRM CVS trees' are the |
| 37 |
development trees for modular X.org (X.org 7, is that?). |
| 38 |
|
| 39 |
Ebuilds for these are available in Portage, they're just hard-masked. |
| 40 |
Myself, I'm not prepared to touch them with a 20-foot/metre pole, but |
| 41 |
perhaps you are. |
| 42 |
|
| 43 |
If not, then it would be better to wait until upstream stabilizes a |
| 44 |
release, and the ebuilds stabilize to at least ~arch. Perhaps the Xorg |
| 45 |
site has a target date for the next release; I haven't looked. I would |
| 46 |
at least imagine that their development mailing list would give a better |
| 47 |
idea as to how close to release they might be. |
| 48 |
|
| 49 |
I'm happy to wait, but that's just my opinion, and it's your choice what |
| 50 |
you decide to do. |
| 51 |
|
| 52 |
HTH, |
| 53 |
Holly |
| 54 |
-- |
| 55 |
gentoo-user@g.o mailing list |
Archives