linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: "Timothy A. Seufert" <tas@mindspring.com>
Cc: Gareth Hughes <gareth@valinux.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: r128 DRI driver now fully functional on PPC
Date: Fri, 23 Feb 2001 13:19:11 +0100	[thread overview]
Message-ID: <3A96553F.B0485736@iiic.ethz.ch> (raw)
In-Reply-To: v04220800b6bbb8f01525@[10.0.0.42]


"Timothy A. Seufert" wrote:

> 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?

http://n.ethz.ch/student/daenzerm/download/DRI/XF86Config

is what I use on my Pismo.


Beware that I have merged in locally some fixes from the trunk which seem to
help for some problems I had - Gareth, will we merge the branch into the trunk
anytime soon or should I commit those to the branch?

The only issues I'm seeing now are broken lighting textures in quake-gl,
missing texture in xtraceroute and garbage at the top of the framebuffer
periodically. The last also causes a delay so I suspect it's some DMA
operation going wrong and the driver hitting a timeout, unfortunately I don't
have time to track it down and probably won't have for weeks. :(

Otherwise it works great for me!


--
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/

  parent reply	other threads:[~2001-02-23 12:19 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
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 [this message]
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=3A96553F.B0485736@iiic.ethz.ch \
    --to=michdaen@iiic.ethz.ch \
    --cc=gareth@valinux.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tas@mindspring.com \
    /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).