All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marvin Justice <mjustice@austin.rr.com>
To: Chris Meadors <clubneon@hereintown.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re:[OT] What Athlon chipset is most stable in Linux?
Date: Wed, 14 Nov 2001 09:28:35 -0600	[thread overview]
Message-ID: <01111409283504.00746@bozo> (raw)
In-Reply-To: <Pine.LNX.4.40.0111140823040.88-100000@rc.priv.hereintown.net>
In-Reply-To: <Pine.LNX.4.40.0111140823040.88-100000@rc.priv.hereintown.net>

On Wednesday 14 November 2001 07:27 am, Chris Meadors wrote:
> Anyway, to keep this kinda kernel related.  How well supported are the
> FireGL cards?  That is DRM wise, and of course X to go with that.
>
> -Chris

Drivers are distributed pretty much the same way as nVidia, ie., as a binary 
core along with the necessary wrappers to compile for new kernels, private 
libGL.so, etc.  Aside from that, we've generally had pretty positive 
experiences.

These aren't quake cards; in fact the demo1 fps are  surprisingly low. In 
serious OpenGL benchmarks, however,  
(http://www.specbench.org/gpc/opc.static/opcview.htm ) they're currently the 
fastest cards available for Linux by a long shot.

I think FGL is what people at ILM, Dreamworks, Digital Domain etc. are using 
at the moment in the gradual shift toward Linux on the artist's desktop. Not 
cheap --- unless you've already forked over $16K for Maya ;-)

-- 
Marvin Justice
Software Developer
BOXX Technologies, Inc.
www.boxxtech.com
512-235-6318 (V)
512-835-0434 (F)

  reply	other threads:[~2001-11-14 15:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 13:19 What Athlon chipset is most stable in Linux? Martin Eriksson
2001-11-13 16:06 ` Pascal Schmidt
2001-11-13 17:12 ` Jeffrey W. Baker
2001-11-13 21:08 ` Calin A. Culianu
2001-11-13 21:37   ` Brian
2001-11-13 22:18     ` Paul G. Allen
2001-11-13 22:39       ` Calin A. Culianu
2001-11-14  1:27       ` Stuart Young
2001-11-14 20:08         ` Calin A. Culianu
2001-11-14  2:32     ` David S. Miller
2001-11-14  3:05       ` Dan Hollis
2001-11-14  3:11         ` David S. Miller
2001-11-14  3:11       ` Brian
2001-11-14  2:55         ` Joel Jaeggli
2001-11-14 20:04           ` Calin A. Culianu
2001-11-14  3:13         ` David S. Miller
2001-11-14 14:23           ` Mike Dresser
2001-11-14  3:11       ` Dan Hollis
2001-11-14  3:16         ` David S. Miller
2001-11-14 16:54           ` Ion Badulescu
2001-11-15  1:03           ` Paul G. Allen
2001-11-15  1:15             ` Dan Hollis
2001-11-15  1:23             ` Stuart Young
2001-11-15  1:51               ` Paul G. Allen
     [not found]             ` <20011116144835.A22537@weta.f00f.org>
2001-11-20  7:43               ` Paul G. Allen
2001-11-20 16:49                 ` Gérard Roudier
2001-11-15  0:45         ` Stuart Young
2001-11-15  9:58           ` David S. Miller
2001-11-14  3:19       ` Marvin Justice
2001-11-14 13:27         ` Chris Meadors
2001-11-14 15:28           ` Marvin Justice [this message]
2001-11-14  6:38   ` DevilKin
2001-11-13 21:19 ` Dan Hollis
2001-11-14  2:29   ` David S. Miller
2001-11-14 10:51     ` Alan Cox
2001-11-14 10:48       ` David S. Miller
2001-11-15 19:57       ` Marek Mentel
2001-11-15 13:04         ` David S. Miller

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=01111409283504.00746@bozo \
    --to=mjustice@austin.rr.com \
    --cc=clubneon@hereintown.net \
    --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 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.