public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3D video card recommendations
Date: Mon, 07 Nov 2005 07:42:51 -0500	[thread overview]
Message-ID: <1131367371.14381.91.camel@localhost.localdomain> (raw)
In-Reply-To: <1131349343.2858.11.camel@laptopd505.fenrus.org>

On Mon, 2005-11-07 at 08:42 +0100, Arjan van de Ven wrote:

> people who buy a 3D card for linux that depends on a closed source
> module take a few risks, and they should be aware of them (I suspect
> they are) so let me make some of them explicit:

Are there good 3D cards that don't depend on a proprietary module, that
can run on a AMD64 board?  That was pretty much my questing to begin
with :)
 
> 
> By buying a piece of hardware that requires a closed module you take the
> risk that one of the following can happen at any time

Yep, I know all these, since I've been a NVidia user for some time.  But
NVidia was good enough for my needs since the only times I needed 3D was
when I wasn't playing with experimental kernels.

> 
> 1) The vendor in the future stops considering linux important and you're
> stuck with old kernels; for example as a side-effect of getting a good
> deal to supply graphics chips to a certain game console maker

I was able to get some hacks out for NVidia on some new kernels before
they were official released.  But they were not great, just worked.

> 2) The vendor in the future stops considering the hardware you bought
> important enough to spend time on; after all they got their cash and the
> product cycles for consumer hardware are often in the 3 to 6 month
> timeframe. Result: you're stuck with old kernels.

So far NVidia is good at having one driver to do most of their boards.
It would take a major design change of a model to stop this, and by
then, I would probably have a new video card anyway.

> 3) The vendor gets sued and convicted for GPL violations and stops doing
> linux as a result. (not saying it will happen, but it sure is a risk you
> are taking)

Could happen, but I doubt it.  This might happen if one of the above do
first :)

> 4) The linux kernel developers change the kernel in a way that the
> module in question no longer is possible and the vendor stops updating
> the driver

I've also hacked my kernel to get NVidia working. (Changing
EXPORT_SYMBOL_GPL back to EXPORT_SYMBOL)  It's ok as long as I'm using
this just for myself.  Which currently I am.

> 5) The vendor goes out of business and thus stops updating the driver

MS folks would have the same problem.

> 6) The vendor doesn't release an x86-64 binary (or other architecture)
> and your next PC can't use the module anymore

Hmm, x86-64 _is_ what I'll be using this on :-/

> 7) The vendor starts charging money for the driver or updates thereof.

Good way to lose customers.

> 
> Open source is not just something for developers, but also for users. It
> means that you or anyone else can keep the open driver going even when
> the manufacturer stops doing so. By using a closed driver you get all
> the disadvantages of the open source model (yes there are some just that
> normally the benefits outweigh them by far) without getting the gains.
> Be very sure you want to do this before spending your hard earned money
> on hardware that doesn't work without closed drivers.
> 

I totally agree with you on this, that's why my question was about a
good "Open Source" 3D card in the first place.  I want to try out 3D on
Ingo's RT patch set and NVidia (because of the above that you mentioned)
doesn't cut it anymore.  I've heard that the Radeon open source drive
isn't too bad so I went with them. I don't need the best 3D, but I do
need something.

So you are right.  I've been a loyal NVidia customer for several years
now, but since there is no alternative of a reliable 3D driver for them,
I had to leave them to do what I needed. Now they risk me never going
back if I find out that I like ATI better.

-- Steve



  reply	other threads:[~2005-11-07 12:43 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 [this message]
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
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=1131367371.14381.91.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=arjan@infradead.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