linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Timothy A. Seufert" <tas@mindspring.com>
To: Gareth Hughes <gareth@valinux.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: r128 DRI driver now fully functional on PPC
Date: Thu, 22 Feb 2001 23:07:31 -0800	[thread overview]
Message-ID: <v04220800b6bbb8f01525@[10.0.0.42]> (raw)
In-Reply-To: <3A76769B.87242FAA@valinux.com>


At 7:08 PM +1100 1/30/01, Gareth Hughes wrote:
>I've just committed the last of the updates required to get full hardware
>accelerated 3D rendering with the ATI Rage 128 on PowerPC.  Many
>thanks to Paul
>Mackerras for allowing me to hack away on his machine over the last week!
>
>The code is available on the ati-pcigart-0-0-1-branch in the DRI CVS
>repository.  Please feel free to check it out and report any
>problems you have.

Gareth (& everybody on the ppc dev list),

I've been trying to get this to work on a B&W G3 with a 100 MHz R128
PCI OEM card.

I'm getting things to build OK, but I did experience a couple
problems along the way.  The first was an old distribution /
compiler; when compiled by it, the X server would crash during
startup.  Reinstalling with LinuxPPC 2000 Q4 cured that.

The second is that the DRM kernel modules fail to build against the
2.2.18 headers.  A function in vm.c (I think) tries to access a field
named 'virtual' in struct page, which simply isn't there in 2.2.18.
The #if statements surrounding the code seem to be deliberately
compiling it only if the kernel is a 2.2 series, so I'm not sure what
is going on.  So I shifted over to the PPC 2.4 BK kernels and got
everything to build OK that way.

Where I'm at now is that the X server loads and runs (quite well I
might add), automatically loads the r128.o kernel module, and (in the
logfile) claims to have enabled direct rendering.  However, both
windowed and fullscreen GL apps are very clearly not being
accelerated.  Frame rates are obviously software renderer type frame
rates, and apps which check for multitexture capability complain that
it isn't there.

Any suggestions?  If anybody wants to see some logs from the server
starting up, I'll supply 'em.  Also, if anybody out there has gotten
this working, could you send me your XF86Config so I can make sure I
didn't do something silly to mine?

   Tim Seufert

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

  parent reply	other threads:[~2001-02-23  7:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30  8:08 r128 DRI driver now fully functional on PPC Gareth Hughes
2001-01-31 11:49 ` Benjamin Herrenschmidt
2001-01-31 14:54   ` [linux-fbdev] " Andreas Hundt
2001-01-31 18:32     ` Michel Dänzer
2001-01-31 18:43       ` Geert Uytterhoeven
2001-01-31 18:53         ` Michel Dänzer
2001-01-31 19:14         ` Andreas Hundt
2001-01-31 16:49   ` Kostas Gewrgiou
2001-01-31 18:26   ` Michel Dänzer
2001-02-23  7:07 ` Timothy A. Seufert [this message]
2001-02-23 10:02   ` Gareth Hughes
2001-02-25  8:32     ` Timothy A. Seufert
2001-02-26  9:39       ` Michel Dänzer
2001-02-26 10:06         ` Gareth Hughes
2001-02-26 10:21           ` Michel Dänzer
2001-02-26 10:28             ` Gareth Hughes
2001-02-27 10:03               ` Timothy A. Seufert
2001-02-27 11:39                 ` Gareth Hughes
2001-02-27 21:43                   ` Michel Dänzer
2001-02-23 12:19   ` Michel Dänzer
2001-02-23 12:23     ` Gareth Hughes
2001-02-23 12:33       ` 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='v04220800b6bbb8f01525@[10.0.0.42]' \
    --to=tas@mindspring.com \
    --cc=gareth@valinux.com \
    --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).