From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Eddy Petrisor <eddy.petrisor@gmail.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
DebianPPC <debian-powerpc@lists.debian.org>
Subject: Re: Laptop sleep & current "git" tree
Date: Sat, 07 May 2005 10:06:00 +1000 [thread overview]
Message-ID: <1115424360.23610.21.camel@gaston> (raw)
In-Reply-To: <427BE8B0.5030802@gmail.com>
On Sat, 2005-05-07 at 00:59 +0300, Eddy Petrisor wrote:
> Benjamin Herrenschmidt wrote:
> >
> > I don't know this problem, what happens precisely and what model of
> > radeon chip do you have ?
> >
> I am just interfering as you talked about radeon models; is there any
> good news regarding the >9600 chipsets?
> I know there was a project (R300 iirc) that wanted to make a driver, but
> progress was slow or non-existant last time I heard about it.
There is a fully working 2D driver and there is an in-progress 3D driver
based on some sort of reverse engineering. It works weel enough for some
things like tuxracer, pinball or bzflag :) You probably need to get all
sort of up to date CVS things to get it to work though (X.org, DRI and
Mesa)
Ben.
next prev parent reply other threads:[~2005-05-07 0:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 22:15 Laptop sleep & current "git" tree Benjamin Herrenschmidt
2005-05-03 6:37 ` Colin Leroy
2005-05-03 23:50 ` Benjamin Herrenschmidt
2005-05-04 6:35 ` Colin Leroy
2005-05-07 12:06 ` Colin Leroy
2005-05-08 4:32 ` John Steele Scott
2005-05-08 9:39 ` Colin Leroy
2005-05-08 22:35 ` John Steele Scott
2005-05-09 6:35 ` Colin Leroy
2005-05-11 0:03 ` John Steele Scott
2005-05-03 8:36 ` David Woodhouse
2005-05-03 22:22 ` Ian Wienand
2005-05-03 23:41 ` Benjamin Herrenschmidt
2005-05-03 23:48 ` Ian Wienand
2005-05-04 0:03 ` Benjamin Herrenschmidt
2005-05-06 21:59 ` Eddy Petrisor
2005-05-07 0:06 ` Benjamin Herrenschmidt [this message]
2005-05-07 10:09 ` Jerome Glisse
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=1115424360.23610.21.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=eddy.petrisor@gmail.com \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.