public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] About ATI drivers in X.org 7
Date: Fri, 07 Oct 2005 11:53:21 +0200	[thread overview]
Message-ID: <43464591.8020308@planet.nl> (raw)
In-Reply-To: <4346199F.3010404@maestroprogramador.com>

Rafael Fernández López schreef:
> Hi,
> 
> I've read something somewhere that have amazed me... Is X.org 
> developing new ATI drivers, better far from ATI.com ?

Yes and no... I think what you're talking about is most likely the open
source r300 drivers (similar in effect to the open source 'radeon'
kernel drivers that are available for the 9500 and below).

More information can be found on these drivers here:

http://r300.sourceforge.net/R300.php

As far as I know, although the r300 project's code is available to X.org
(and in fact has been accepted into the CVS tree), the project itself is not
associated with, or rather is separate from, the X.org project itself.

> 
> If that's affirmative... We will be able to use Damage extension (and
>  Composite extension) with ati rendering ?

No idea, since I don't know what the Damage extension is/does, and afaik
the Composite extension is not yet complete or stable, so it doesn't
'matter' whether it works atm-- ATI themselves don't want to 'waste'
resources on supporting Composite until it's done, so I can't imagine
that the Open Source project is going to focus on it yet either (having
less resources and information than ATI themselves).

> 
> And when is X.org going to be able on portage ?

As noted on the r300 site, 'The latest source code is available directly
from Xorg, Mesa and DRM CVS trees.'

I would assume that 'the Xorg, Mesa and DRM CVS trees' are the
development trees for modular X.org (X.org 7, is that?).

Ebuilds for these are available in Portage, they're just hard-masked.
Myself, I'm not prepared to touch them with a 20-foot/metre pole, but
perhaps you are.

If not, then it would be better to wait until upstream stabilizes a
release, and the ebuilds stabilize to at least ~arch. Perhaps the Xorg
site has a target date for the next release; I haven't looked. I would
at least imagine that their development mailing list would give a better
idea as to how close to release they might be.

I'm happy to wait, but that's just my opinion, and it's your choice what
you decide to do.

HTH,
Holly
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-10-07  9:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07  6:45 [gentoo-user] About ATI drivers in X.org 7 Rafael Fernández López
2005-10-07  9:53 ` Holly Bostick [this message]
2005-10-07 12:58   ` Rafael Fernández López
2005-10-07 14:46     ` Luis Felipe Strano Moraes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43464591.8020308@planet.nl \
    --to=motub@planet.nl \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox