From: Nicolas Mailhot <nicolas.mailhot@laposte.net>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Joshua Kugler <joshua.kugler@uaf.edu>,
linux-kernel@vger.kernel.org,
David Chow <davidchow@shaolinmicro.com>
Subject: Re: Linux drivers management
Date: Mon, 06 Feb 2006 20:58:58 +0100 [thread overview]
Message-ID: <1139255939.20009.46.camel@rousalka.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0602061420400.17351@chaos.analogic.com>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
Le lundi 06 février 2006 à 14:21 -0500, linux-os (Dick Johnson) a
écrit :
> Right now, there are really too many drivers in the kernel.
> The kernel should have a stable API for drivers and they
> should be in a separate tree, either on the Web or on a
> distribution disc. There are many drivers that are as old
> as Linux! The 3c501.c and 3c503.c are examples. You can't
> remove them from the kernel without invoking a thousand
> angry responses. These boards and the ne*.c network boards
> just won't go away!
This is another proof in-kernel maintenance is cheaper.
If out-of-tree drivers where lower maintenance like it's claimed, they'd
have a lower attrition rate than in-kernel stuff.
--
Nicolas Mailhot
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2006-02-06 20:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 18:31 Linux drivers management Nicolas Mailhot
2006-02-06 18:56 ` Yaroslav Rastrigin
2006-02-06 19:02 ` Joshua Kugler
2006-02-06 19:17 ` Yaroslav Rastrigin
2006-02-06 19:39 ` Martin Mares
2006-02-06 19:56 ` Jan-Benedict Glaw
2006-02-06 19:53 ` Jan-Benedict Glaw
2006-02-06 20:04 ` Jesper Juhl
2006-02-06 23:52 ` Bernd Petrovitsch
2006-02-06 19:21 ` linux-os (Dick Johnson)
2006-02-06 19:46 ` Michael Krufky
2006-02-06 19:58 ` Nicolas Mailhot [this message]
2006-02-06 23:16 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2006-02-07 4:42 linux
2006-02-07 16:18 ` Eric W. Biederman
2006-02-07 19:45 ` David Chow
2006-02-07 20:03 ` Kyle Moffett
2006-02-07 22:15 ` Theodore Ts'o
2006-02-08 0:52 ` David Chow
2006-02-08 4:02 ` Theodore Ts'o
2006-02-08 9:46 ` Bernd Petrovitsch
2006-02-09 6:09 ` Lee Revell
2006-02-08 1:06 ` Alan Cox
2006-02-08 8:26 ` Denis Vlasenko
2006-02-11 18:47 ` Andrew James Wade
2006-02-06 19:30 Nicolas Mailhot
2006-02-06 9:45 David Chow
2006-02-06 10:05 ` Michal Schmidt
2006-02-06 16:50 ` David Chow
2006-02-06 16:55 ` Randy.Dunlap
2006-02-06 19:45 ` Alan Cox
2006-02-06 19:46 ` Jesper Juhl
2006-02-06 10:08 ` Jes Sorensen
2006-02-06 16:52 ` David Chow
2006-02-06 17:03 ` Pedro Alves
2006-02-06 17:35 ` Geert Uytterhoeven
2006-02-06 17:42 ` Jes Sorensen
2006-02-06 16:56 ` Christoph Hellwig
2006-02-07 11:36 ` Denis Vlasenko
2006-02-07 13:22 ` Christoph Hellwig
2006-02-06 19:51 ` Greg KH
2006-02-06 21:38 ` Jim Crilly
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=1139255939.20009.46.camel@rousalka.dyndns.org \
--to=nicolas.mailhot@laposte.net \
--cc=davidchow@shaolinmicro.com \
--cc=joshua.kugler@uaf.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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;
as well as URLs for NNTP newsgroup(s).