From: linux@horizon.com
To: davidchow@shaolinmicro.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux drivers management
Date: 6 Feb 2006 23:42:04 -0500 [thread overview]
Message-ID: <20060207044204.8908.qmail@science.horizon.com> (raw)
> Is there any work in Linux undergoing to separate Linux drivers and the
> the main kernel, and manage drivers using a package management system
> that only manages kernel drivers and modules? If this can be done, the
> kernel maintenance can be simple, and will end-up with a more stable
> (less frequent changed) kernel API for drivers, also make every
> developers of drivers happy.
Not very seriously. Kernel developers really like the ability to change
every user of a kernel programming interface within a single source tree.
Breaking it up would make it harder to change the device driver interface
when necessary. (It's already hard enough; nobody does it for fun.)
Also, a hardware manufacturer looking for a "stable API" is often
really looking for a stable *binary* interface because they want to
ship binary-only drivers.
The Linux developers are quite opposed to that, for a variety of excellent
reasons I won't bother enumerating. Linus has said he'll (grudgingly)
allow it, but won't lift a finger to help. Linux development sailed
away from the idea of a stable binary interface years ago, and isn't
looking back.
next reply other threads:[~2006-02-07 4:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 4:42 linux [this message]
2006-02-07 16:18 ` Linux drivers management 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
-- strict thread matches above, loose matches on Subject: below --
2006-02-06 19:30 Nicolas Mailhot
2006-02-06 18:31 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
2006-02-06 23:16 ` Gene Heskett
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=20060207044204.8908.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=davidchow@shaolinmicro.com \
--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