From: Michel Dänzer <michdaen@iiic.ethz.ch>
To: Steven Hanley <sjh@wibble.net>
Cc: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: dri status? (agpgart?)
Date: Sun, 21 Jan 2001 23:21:56 +0100 [thread overview]
Message-ID: <3A6B6104.4935B5CA@iiic.ethz.ch> (raw)
In-Reply-To: 20010121223637.A32549@wibble.net
Steven Hanley wrote:
> I am just now grabbing the cvs repository from dri.sourceforge.net to see if
> I can get dri running on my pismo, now I am wondering what the current
> status is?
>
> (I am of course doing this because gareth hughs was at linux.conf.au over
> the last few days, and I was completely blown away by the performance of 3d
> stuff on his laptop (it was absolutely amazing to say the least))
Yes, it will rock once it works. :)
> Last I heard for ppc was that we could do dri but not the agpgart stuff,
> which means it doesnt go quite as fast as we may wish
That was about the situation a few months ago. Currently, the r128 DRI doesn't
work without AGP GART.
PCI GART support is currently being developed in a branch of the DRI CVS, but
I haven't got it to work on my Pismo yet (see the other thread about 'PPC
lockups'). As always, any help is much appreciated! :)
As for AGP GART, once PCI GART works I may have a stab at that. But I don't
expect it to give a substantial performance boost.
> (no mtrr write combining or some such)
This is an ia32 thing and doesn't affect us.
Michel
--
Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \ XFree86 and DRI project member
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-01-21 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-21 11:36 dri status? (agpgart?) Steven Hanley
2001-01-21 22:21 ` Michel Dänzer [this message]
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=3A6B6104.4935B5CA@iiic.ethz.ch \
--to=michdaen@iiic.ethz.ch \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sjh@wibble.net \
/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;
as well as URLs for NNTP newsgroup(s).