From: James Courtier-Dutton <James@superbug.co.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: John Richard Moser <nigelenki@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: Driver model.. expel legacy drivers?
Date: Sat, 14 Oct 2006 12:19:15 +0100 [thread overview]
Message-ID: <4530C7B3.6030805@superbug.co.uk> (raw)
In-Reply-To: <20061014075625.GA30596@stusta.de>
Adrian Bunk wrote:
>> ...
>> This brings up a few potential questions:
>>
>> - Will this eventually be necessary to an absolute? Will 100M
>> tarballs and hundreds of thousands of drivers be unmanageable in a
>> tight, ABI-unstable monolith 10 years from now?
>
> "hundreds of thousands of drivers" won't happen during my lifetime.
>
> If the kernel size only doubles to 100 MB that's no problem.
>
>> - Would it ACTUALLY be worthwhile, given such a scenario, to expel
>> drivers out of the tree to glue on by a static, somewhat slower but
>> workable ABI so nobody has to touch the code ever?
>
> Documentation/stable_api_nonsense.txt describes why this is nonsense.
>
stable api is even nonsense for Windows, which tries to have a stable
api for drivers. For example, manufacturers are having to write Vista
specific drivers, because their old Windows XP drivers don't work on
Vista. E.g. Creative sound cards.
next prev parent reply other threads:[~2006-10-14 11:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 3:18 Driver model.. expel legacy drivers? John Richard Moser
2006-10-14 7:56 ` Adrian Bunk
2006-10-14 11:19 ` James Courtier-Dutton [this message]
2006-10-14 15:04 ` John Richard Moser
2006-10-14 18:54 ` Horst H. von Brand
2006-10-14 20:48 ` John Richard Moser
2006-10-15 15:31 ` Jan Engelhardt
2006-10-14 21:14 ` Kevin K
2006-10-14 21:44 ` John Richard Moser
2006-10-15 0:03 ` Alan Cox
2006-10-14 23:51 ` John Richard Moser
2006-10-15 1:24 ` Kevin K
2006-10-15 1:51 ` Alistair John Strachan
2006-10-15 14:33 ` Alan Cox
2006-10-16 9:39 ` Kasper Sandberg
2006-10-16 14:13 ` Lee Revell
2006-10-16 19:04 ` 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=4530C7B3.6030805@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
/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