From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: jimwclark@ntlworld.com
Cc: Rik van Riel <riel@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Driver Model 2 Proposal - Linux Kernel Performance v Usability
Date: Thu, 4 Sep 2003 23:41:22 +0200 [thread overview]
Message-ID: <200309042341.22702.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <200309042212.25052.jimwclark@ntlworld.com>
Heh. You want stable plugin API.
It will always end as bloat:
(a) you add plugin API
(b) its not sufficient, so you add revision 1 of the API
(you still have to support rev 0 because some plugins are binary-only)
(c) its not sufficient, so you add revision 2 of the API
(now you have 3 versions of API to maintain)
...
Alternatively you can start with over-designed API from the beginning :-).
--bartlomiej
On Thursday 04 of September 2003 23:12, James Clark wrote:
> Why would binary drivers be any harder to debug than the existing binary
> kernel. If you want to debug something use the source code. My proposal
> doesn't remove the need for quality public source code but it does isolate
> the kernel components and allow for 'plugin' use on different kernels both
> old and new.
>
> If a relatively small kernel component can be turned on/off and upgraded at
> will, without changing ANYTHING else, this would be a big step forward.
>
> James
>
> On Thursday 04 Sep 2003 9:29 pm, you wrote:
> > On Thu, 4 Sep 2003, James Clark wrote:
> > > I'm very surprised by the number of posts that have ranted about
> > > Open/Close source, GPL/taint issues etc. This is not about source code
> > > it is about making Linux usable by the masses.
> >
> > How would "making it easier to include impossible to debug
> > device drivers" help towards your goal of making Linux more
> > usable ?
next prev parent reply other threads:[~2003-09-04 21:40 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1062637356.846.3471.camel@cube>
2003-09-04 20:14 ` Driver Model 2 Proposal - Linux Kernel Performance v Usability James Clark
2003-09-04 20:27 ` Mike Fedyk
2003-09-04 21:16 ` James Clark
2003-09-04 21:50 ` Mike Fedyk
2003-09-04 22:10 ` insecure
2003-09-04 22:01 ` jdow
2003-09-04 20:29 ` Rik van Riel
2003-09-04 21:12 ` James Clark
2003-09-04 21:40 ` Alan Cox
2003-09-04 21:41 ` Bartlomiej Zolnierkiewicz [this message]
2003-09-04 22:19 ` Jamie Lokier
2003-09-04 21:29 ` Richard B. Johnson
2003-09-04 21:51 ` James Clark
2003-09-04 22:06 ` Alan Cox
2003-09-04 22:10 ` Martin Mares
2003-09-04 22:23 ` Gustav Petersson
2003-09-05 17:52 ` Valdis.Kletnieks
2003-09-05 18:31 ` James Clark
2003-09-05 18:59 ` Martin Schlemmer
2003-09-05 19:12 ` Dale P. Smith
2003-09-05 19:45 ` Stan Bubrouski
2003-09-05 19:59 ` Richard B. Johnson
2003-09-05 20:01 ` James Clark
2003-09-05 20:08 ` Mike Fedyk
2003-09-05 21:15 ` Valdis.Kletnieks
2003-09-05 23:19 ` Bernd Eckenfels
2003-09-10 20:50 ` Timothy Miller
2003-09-10 20:48 ` Richard B. Johnson
2003-09-10 23:22 ` James Clark
2003-09-10 23:58 ` Greg KH
2003-09-12 20:51 ` Timothy Miller
2003-09-12 20:55 ` Tim Hockin
2003-09-15 11:39 ` Richard B. Johnson
2003-09-05 20:53 Chad Kitching
2003-09-05 23:30 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2003-09-04 22:41 Chad Kitching
2003-09-03 17:53 James Clark
2003-09-03 17:49 ` Andre Hedrick
2003-09-03 18:23 ` Guillaume Morin
2003-09-04 4:10 ` Andre Hedrick
2003-09-03 18:35 ` Guillaume Morin
2003-09-03 19:30 ` Andre Hedrick
2003-09-03 18:18 ` Greg KH
2003-09-03 18:23 ` Richard B. Johnson
2003-09-03 18:49 ` Patrick Mochel
2003-09-03 18:58 ` Gábor Lénárt
2003-09-03 20:18 ` Christoph Hellwig
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=200309042341.22702.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=jimwclark@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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).