From: Michel Dänzer <daenzer@relog.ch>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: How to get up-to-speed on the 3D / DRI in Rage 128
Date: Tue, 08 Aug 2000 18:20:17 +0200 [thread overview]
Message-ID: <39903341.6195EF62@relog.ch> (raw)
In-Reply-To: 3990310E.6C3EF59B@ivey.uwo.ca
"Kevin B. Hendricks" wrote:
> > > - DRI patches?
> >
> > Yep. What I'm running is the DRI CVS trunk (which is basically X 4.0.1 and
> > some DRI changes) and a patch that I've posted to dri-devel. If you can't
> > get it from there, I can send it to you privately or put it up for...
>
> Yes, I found patches named drm-r128.diff and drm_panning.patch you posted
> recently to the dev list.
The second one is just for aty128fb's panning and not directly related to DRI.
The first one is to get the DRM kernel module working, but you can also build
that from the DRI tree - read below ...
> Where or how do I go about getting the DRI CVS trunk? Is this a project on
> sourceforge? Is there anonymous cvs access?
The great news is that I've just been added to the DRI project at sourceforge
(http://dri.sourceforge.net). I'll start a PPC branch which you should be able
to just checkout and build and it should work (and which will eventually be
integrated into the trunk of course :).
I'll post the announcement for that branch to this list as well.
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-08 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-08 15:48 How to get up-to-speed on the 3D / DRI in Rage 128 Kevin B. Hendricks
2000-08-08 15:59 ` Michel Dänzer
2000-08-08 16:10 ` Kevin B. Hendricks
2000-08-08 16:20 ` Michel Dänzer [this message]
2000-08-08 21:26 ` Michel Dänzer
2000-08-09 1:10 ` Giuliano Pochini
2000-08-08 19:22 ` Michel Dänzer
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=39903341.6195EF62@relog.ch \
--to=daenzer@relog.ch \
--cc=daenzerm@student.ethz.ch \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).