From: Dominik Karall <dominik.karall@gmx.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Tim Fairchild <tim@bcs4me.com>,
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, 4 Sep 2004 23:22:47 +0200 [thread overview]
Message-ID: <200409042322.50478.dominik.karall@gmx.net> (raw)
In-Reply-To: <1094327788.6575.209.camel@krustophenia.net>
so which (in this case) graphic card should we buy? i bought my nvidia card,
because i knew that nvidia hands out linux drivers, even if they are binary
only, but i knew that they do, so i didn't want to buy another card and
realize afterwards that it absolutely isn't supported under linux.
regards,
dominik
On Saturday 04 September 2004 21:56, Lee Revell wrote:
> On Sat, 2004-09-04 at 05:54, Tim Fairchild wrote:
> > The nvidia module compiles fine with the non mm kernel but will
> > not compile with the mm patches for me.
>
> The nvidia module is binary-only. You are not compiling it, AIUI the
> installer fetches the binary module from the nvidia site and builds some
> wrappers. Even if this process were to succeed the result would almost
> certainly not work. This is the reason you need open source software.
>
> Judging from all the tainted-kernel OOPS'es that get posted here, it
> would appear that the majority of Linux users are perfectly willing to
> buy hardware that requires binary-only drivers. People do not seem to
> understand that there is absolutely NO incentive for vendors to open
> their source if you would buy it just the same with a binary driver!
>
> I bet 99.9% of the people who signed that stupid petition already own
> freaking ATI hardware. The people yelling the loudest seem to be those
> who didn't realize the hardware wasn't Linux compatible when they bought
> it, when it would have taken 10 seconds to find out. Why should they
> give you an open source driver now, when you were perfectly willing to
> buy it without one? Because you threaten not to buy another?
> Bwahahahahaha.
>
> The only kind of democracy hardware vendors understand is voting with
> your wallet. Personally I don't care, all the drivers I use are open
> source, but the whining is getting tiresome.
>
> Lee
next prev parent reply other threads:[~2004-09-04 21:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 0:17 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
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 [this message]
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=200409042322.50478.dominik.karall@gmx.net \
--to=dominik.karall@gmx.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--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
all inboxes | Powered by JetHome®