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