From: Lee Revell <rlrevell@joe-job.com>
To: Tim Fairchild <tim@bcs4me.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Sid Boyce <sboyce@blueyonder.co.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: NVIDIA Driver 1.0-6111 fix
Date: Sat, 04 Sep 2004 17:22:29 -0400 [thread overview]
Message-ID: <1094332949.6575.360.camel@krustophenia.net> (raw)
In-Reply-To: <200409050702.29007.tim@bcs4me.com>
On Sat, 2004-09-04 at 17:02, Tim Fairchild wrote:
> Users don't really care about open and closed source. They just want
> to play quake 3 (etc).
>
I have never understood why these people don't just run Windows. I have
also never understood why people make so much noise about having to use
a closed source driver to play A CLOSED SOURCE GAME! What's next, a
petition to open the UT2004 source? Sheesh...
> I've never had an oops that was specifically caused by the nvidia module, tho
> I suppose it does happen.
And I have never seen one either. I am just using the OOPS'es as an
indication of how many Linux users use this driver. It's WAY more than
I expected. The open source nv.o module works fine for me, I don't see
how the 2D would need to be faster, or how you would even tell the
difference.
I suspect many of these users are ricers who tweak CFLAGS and compare
benchmark scores all day, and cannot bear to use the open source driver
if it will make their machine 1% slower. I was surprised to find that
apparently there are open source ATI 3D drivers after all but some
people are petitioning ATI anyway because these 'aren't as good' as the
binary ones. So fix it already, this is open source, and if you can't,
then please learn to write code or STFU.
Lee
next prev parent reply other threads:[~2004-09-04 21:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 0:17 NVIDIA Driver 1.0-6111 fix Sid Boyce
2004-09-04 6:28 ` Prakash K. Cheemplavam
2004-09-04 9:25 ` Dominik Karall
2004-09-04 9:32 ` Sid Boyce
2004-09-04 9:36 ` Christoph Hellwig
2004-09-04 9:54 ` Tim Fairchild
2004-09-04 9:58 ` Christoph Hellwig
2004-09-04 19:56 ` Lee Revell
2004-09-04 21:02 ` Tim Fairchild
2004-09-04 21:22 ` Lee Revell [this message]
2004-09-04 22:09 ` Tim Fairchild
2004-09-05 1:12 ` [OT] " Christian Kujau
2004-09-05 1:52 ` Lee Revell
2004-09-05 2:03 ` Horst von Brand
2004-09-05 3:32 ` [OT] " Lee Revell
2004-09-05 5:29 ` Tim Fairchild
2004-09-05 5:57 ` Lee Revell
2004-09-05 23:20 ` J.A. Magallon
2004-09-06 0:23 ` Lee Revell
2004-09-06 20:54 ` Alessandro Sappia
2004-09-05 12:03 ` Giuseppe Bilotta
2004-09-05 12:04 ` Alan Cox
2004-09-05 13:39 ` Grzegorz Kulewski
2004-09-05 14:37 ` Sid Boyce
2004-09-05 23:29 ` Chris Wedgwood
2004-09-04 21:22 ` Dominik Karall
2004-09-04 21:25 ` Lee Revell
2004-09-04 23:44 ` Paul Jakma
2004-09-05 6:27 ` Sid Boyce
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=1094332949.6575.360.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
--cc=tim@bcs4me.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