From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3D video card recommendations
Date: Wed, 09 Nov 2005 01:34:03 +0000 [thread overview]
Message-ID: <1131500043.25192.125.camel@localhost.localdomain> (raw)
In-Reply-To: <20051108220853.GA26615@merlin.emma.line.org>
On Maw, 2005-11-08 at 23:08 +0100, Matthias Andree wrote:
> I'd rather not count the drivers that have dropped out of open source
> operating systems due to bit rot. If there is no maintainer, the
> hardware will become useless sooner or later. With Linux's rapidly
> changing "moving target" 2.6.X I'd call it sooner rather than later
If there is no maintainer and there is demand for the driver then I
guess the end users need to remember its a development model and not a
charity. The problem should then be self correcting if the docs/driver
are open
> OSS drivers are good iff there is a maintainer - IOW: to the user, the
> maintainer makes the difference, not the driver being open source.
No. If the code is open source the user can get it fixed, if it is
closed source then they are screwed because support is by vendor dictat.
If Nvidia drop TNT2 you can't pay a local consultant to fix it.
Alan
next prev parent reply other threads:[~2005-11-09 1:03 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
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 [this message]
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=1131500043.25192.125.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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