linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: simon@himi.org (Simon Fowler)
To: linux-kernel@vger.kernel.org
Subject: Re: System very unstable
Date: Sun, 29 Sep 2002 22:12:22 +1000	[thread overview]
Message-ID: <20020929121222.GB15961@himi.org> (raw)
In-Reply-To: <3D958EF5.7080300@metaparadigm.com>

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]

On Sat, Sep 28, 2002 at 07:13:57PM +0800, Michael Clark wrote:
> On 09/28/02 18:35, David S. Miller wrote:
> >   From: Felix Seeger <felix.seeger@gmx.de>
> >   Date: Sat, 28 Sep 2002 12:33:21 +0200
> >   
> >   What card is good (performance for games and 
> >   a acceptable licenze for kernel developers)?
> >
> >ATI Radeon is pretty fast and all except the very latest chips have
> >opensource drivers.
> 
> Radeon 7500 is currently the fastest board with an opensource
> driver that supports 3D. 8500 XFree support is currently 2D only,
> although apparently work on the opensource GL driver is underway.
> 
> You can get 3D support for the 8500 if you get a commercial
> binary only X server ( http://www.xig.com/ ) - although I
> guess this is almost as bad as having a binary kernel module
> due to the type of hardware access the X server needs to do.
> 
There's also 3D support for the r200 chip (that drives the 8500) in
the DRI cvs tree (see http://dri.sf.net): I haven't tried it, since
I don't have an 8500, but it's there, and under active development,
and seem to work fairly well.

Simon

-- 
PGP public key Id 0x144A991C, or http://himi.org/stuff/himi.asc
(crappy) Homepage: http://himi.org
doe #237 (see http://www.lemuria.org/DeCSS) 
My DeCSS mirror: ftp://himi.org/pub/mirrors/css/ 

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2002-09-29 12:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-28  9:15 System very unstable Felix Seeger
2002-09-28  9:32 ` Alan Cox
2002-09-28  9:34   ` Felix Seeger
2002-09-28  9:50     ` Thunder from the hill
2002-09-28  9:55       ` Felix Seeger
2002-09-28  9:59         ` David S. Miller
2002-09-28 10:10           ` Thunder from the hill
2002-09-28 10:04             ` David S. Miller
2002-09-28 10:33           ` Felix Seeger
2002-09-28 10:35             ` David S. Miller
2002-09-28 11:02               ` FD Cami
2002-09-28 10:48                 ` David S. Miller
2002-09-28 11:13               ` Michael Clark
2002-09-29  0:00                 ` Elladan
2002-09-29  5:50                   ` Michael Clark
2002-09-29  7:37                     ` Elladan
2002-09-29 12:12                 ` Simon Fowler [this message]
2002-09-28 11:35               ` Thunder from the hill
2002-09-28 11:34                 ` David S. Miller
2002-09-29  0:42                   ` Kristofer T. Karas
2002-09-28 10:08         ` Alan Cox
2002-09-28 10:36           ` Felix Seeger
2002-09-28 12:46         ` Krzysztof Halasa
2002-09-29 18:06           ` Felix Seeger
2002-09-28 10:23     ` Marc Giger
2002-09-28 10:31       ` Felix Seeger
2002-09-29  5:41 Dieter Nützel
2002-09-30  6:47 ` Kristofer T. Karas
2002-10-01 12:32   ` Dieter Nützel

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=20020929121222.GB15961@himi.org \
    --to=simon@himi.org \
    --cc=linux-kernel@vger.kernel.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).