public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Romanick <idr@us.ibm.com>
To: Jerome Glisse <j.glisse@gmail.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 3D video card recommendations
Date: Mon, 07 Nov 2005 08:35:22 -0800	[thread overview]
Message-ID: <436F824A.9080500@us.ibm.com> (raw)
In-Reply-To: <4240b9160511070750t25fab9e2u3c8e2c1414b55ebf@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jerome Glisse wrote:
> On 11/7/05, Ville Syrjälä <syrjala@sci.fi> wrote:
>>On Mon, 07 Nov 2005 12:55:13 +0000, Hugo Mills wrote:
>>
>>>   http://www.xgitech.com/
>>>
>>>   Not the fastest pieces of hardware out there by some way, but they
>>>_do_ have open-source drivers.
>>
>>That's not entirely true. The DRI driver is closed source.
> 
> DRI closed source ? You mean the fglrx driver from ati ?

No.  He means the 3D driver for the Xgi cards.  However, Xgi is
apparently working with some folks in the community to remedy this.  I
haven't heard any updates in a *long* time, so it's possible that things
may have stalled.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDb4JJX1gOwKyEAw8RAs82AJsGOC+O0An18TmxXV7XbjJ+EreTdQCfZf8e
aNljl61xsZ5RGlFu8uSgC68=
=YkIR
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2005-11-07 16:36 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 13:56 3D video card recommendations Steven Rostedt
2005-11-04 15:10 ` Mark Knecht
2005-11-04 15:14   ` Paweł Sikora
2005-11-04 15:22   ` Steven Rostedt
     [not found]     ` <ec92bc30511040730g2ad412ddsb3ac63f701de6c97@mail.gmail.com>
2005-11-04 15:39       ` Anshuman Gholap
2005-11-06 23:46   ` Nix
2005-11-07  7:42 ` Arjan van de Ven
2005-11-07 12:42   ` Steven Rostedt
2005-11-07 12:55     ` Hugo Mills
2005-11-07 14:22       ` Paweł Sikora
2005-11-07 15:07         ` Paweł Sikora
2005-11-07 14:51       ` Ville Syrjälä
2005-11-07 15:50         ` Jerome Glisse
2005-11-07 16:24           ` Gerhard Mack
2005-11-07 16:35           ` Ian Romanick [this message]
2005-11-07 16:41           ` Ville Syrjälä
2005-11-07 14:24     ` Alan Cox
2005-11-07 13:59       ` Xavier Bestel
2005-11-07 16:17       ` Gerhard Mack
2005-11-07 15:20     ` Toon van der Pas
2005-11-07 15:31       ` Arjan van de Ven
2005-11-07 17:35         ` Steven Rostedt
2005-11-08 22:08           ` Matthias Andree
2005-11-08 22:18             ` John Stoffel
2005-11-08 22:37             ` Tue, 8 Nov 2005 23:37:43 +0100
2005-11-09  1:34             ` Alan Cox
2005-11-07 17:00       ` Diego Calleja
2005-11-07 17:30         ` Steven Rostedt
2005-11-07 17:44           ` Gerhard Mack
2005-11-07 17:53             ` Steven Rostedt
2005-11-07 17:56               ` Gerhard Mack
2005-11-07 18:01               ` Mark Knecht
2005-11-07 18:15                 ` Steven Rostedt
2005-11-07 18:31                   ` Mark Knecht
2005-11-07 19:08                     ` Gerhard Mack
2005-11-07 19:09                       ` Mark Knecht
2005-11-07 19:05                 ` Lee Revell
2005-11-07 19:23                   ` Mark Knecht
2005-11-07 19:47                     ` Steven Rostedt
2005-11-12  9:11                     ` Lee Revell
2005-11-07 18:19     ` Joel Jaeggli
2005-11-08 18:59     ` Stefan Seyfried
2005-11-08 19:06       ` Lennart Sorensen

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=436F824A.9080500@us.ibm.com \
    --to=idr@us.ibm.com \
    --cc=j.glisse@gmail.com \
    --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