linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Giuliano Pochini <pochini@denise.shiny.it>
To: 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 21:10:28 -0400	[thread overview]
Message-ID: <3990AF84.9E5FBD5A@denise.shiny.it> (raw)
In-Reply-To: 39902E69.67F50604@relog.ch


> > I have the xf 401 src tar archives and I can get a hold of ani's cvs of the
> > xfree86 tree.
>
> I haven't used Ani's patches, and I seem to be the only one running DRI
> successfully so far. Maybe better try without them first.
>
> > What other patches/fixes do I need to get going?
> >
> > - aty128fb.c patches for panning?
>
> Not needed, you can use the full screen.
>
> > - 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 HTTP download.
>
> (Jack Howarth should have it as well)
>
> > - etc
>
> That's all I can think of ATM.

Please let me understand... I d/l the latest X + DRI patches and I compile
them. If all goes right I get a working X, but how can I use the 3D
acceleration ?  Do I need a patched version of Mesa too, or what ?

Bye.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-08-09  1:10 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
2000-08-08 21:26       ` Michel Dänzer
2000-08-09  1:10   ` Giuliano Pochini [this message]
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=3990AF84.9E5FBD5A@denise.shiny.it \
    --to=pochini@denise.shiny.it \
    --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).