All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Toon van der Pas <toon@hout.vanvergehaald.nl>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3D video card recommendations
Date: Mon, 07 Nov 2005 12:35:06 -0500	[thread overview]
Message-ID: <1131384906.14381.108.camel@localhost.localdomain> (raw)
In-Reply-To: <1131377496.2858.21.camel@laptopd505.fenrus.org>

On Mon, 2005-11-07 at 16:31 +0100, Arjan van de Ven wrote:
> On Mon, 2005-11-07 at 16:20 +0100, Toon van der Pas wrote:
> > On Mon, Nov 07, 2005 at 07:42:51AM -0500, Steven Rostedt wrote:
> > > On Mon, 2005-11-07 at 08:42 +0100, Arjan van de Ven wrote:
> > > 
> > > > 5) The vendor goes out of business and thus stops updating the driver
> > > 
> > > MS folks would have the same problem.
> > 
> > ...which proves the point Arjan is making.
> > 
> > For one, I have an ISDN-adapter which doesn't work with any version of
> > MS-Windows from this millennium (no drivers available), while it's still
> > working great on current Linux kernels.
> 
> 
> well despite your post; the Windows people are a lot better at keeping
> old drivers working (win 9x to a NT based kernel was obviously a huge
> change though). In linux you can use an old driver maybe for 6 months if
> you're lucky.. in windows 6 years is no exception. So the problem is a
> lot bigger in linux for the owner of such a card than it is in windows.
> 

Only if the Linux driver is closed source.  Otherwise, the driver should
be upgraded with the kernel.  Most all open source hardware drivers are
already included in the kernel, and maintained as long as there's
someone that has the device that can maintain it.

-- Steve



  reply	other threads:[~2005-11-07 17:35 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 [this message]
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=1131384906.14381.108.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toon@hout.vanvergehaald.nl \
    /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.