linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Dänzer <daenzer@relog.ch>
To: dri-devel@lists.sourceforge.net
Cc: linuxppc-dev@lists.linuxppc.org
Subject: [ANN] DRI PPC branch
Date: Wed, 09 Aug 2000 14:49:53 +0200	[thread overview]
Message-ID: <39915371.424F9D9B@relog.ch> (raw)


We have started a branch in the DRI CVS repository dedicated to getting the
DRI fully working on PPC. I have added basic information about it on the DRI
CVS web page:

http://dri.sourceforge.net/cvs.html


This is the current status of the branch:

- The r128 GL driver works on some machines (specifically on my Pismo :) with
  either one of the recent kernels from Benjamin Herrenschmidt or with one
  from the 2.4 series.
  Please share your experience with Rage128 (Pro) hardware.

- Colours are wrong, and most things don't look quite as they should yet.

- Performance isn't too exciting yet because the driver runs in PIO mode.


TODO:

- AGP GART support. Badly needed for the r128 driver

- Get the other drivers going (except i810 maybe ;).

- Thoroughly check the modifications for PowerPC (I don't know PPC assembly)


Daryll Strauss assured me that he will gladly add developers to the project
(for CVS write access) who provide sensible patches and agree to the DRI CVS
policy (basically that all development is to be done in branches).

Patches can be submitted to the Patch Manager at the DRI SourceForge Project
Page or to the dri-devel mailing list if they're not too big.


Have fun and be happy,

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/

                 reply	other threads:[~2000-08-09 12:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=39915371.424F9D9B@relog.ch \
    --to=daenzer@relog.ch \
    --cc=daenzerm@student.ethz.ch \
    --cc=dri-devel@lists.sourceforge.net \
    --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).