From: John Richard Moser <nigelenki@comcast.net>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: binary drivers and development
Date: Thu, 10 Mar 2005 17:32:39 -0500 [thread overview]
Message-ID: <4230CB07.3020904@comcast.net> (raw)
In-Reply-To: <16944.49977.715895.8761@wombat.chubb.wattle.id.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Peter Chubb wrote:
>>>>>>"John" == John Richard Moser <nigelenki@comcast.net> writes:
>
>
>
> John> I've done more thought, here's a small list of advantages on
> John> using binary drivers, specifically considering UDI. You can
> John> consider a different implementation for binary drivers as well,
> John> with most of the same advantages.
>
> Almost all these advantages are also present for user-mode drivers...
> and getting drivers out of the kernel, where possible, is a much
> better approach IMHO than trying to maintain a leaky in-kernel
> interface. The problem with in-kernel interfaces, even if set in
> concrete, is that any binary driver can go outside the interface ---
> there's no encapsulation --- and so break when the kernel changes.
>
CPL=3 scares me; context switches are expensive. can they have direct
hardware access? I'm sure a security model to isolate user mode drivers
could be in place. . .
. . . huh. Xen seems to run Linux at CPL=3 and give direct hardware
access, so I guess user mode drivers are possible *shrug*. Linux isn't
a microkernel though.
> Peter C
>
>
>
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
Creative brains are a valuable, limited resource. They shouldn't be
wasted on re-inventing the wheel when there are so many fascinating
new problems waiting out there.
-- Eric Steven Raymond
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD4DBQFCMMsGhDd4aOud5P8RAjoOAJ9Owgnd5QOp9MfrQ8PzOLAt/A7k+wCYmxLc
wvXLkQX84Z2PF2J4oEIbVA==
=wi8f
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-03-10 22:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 16:28 binary drivers and development John Richard Moser
2005-03-10 16:48 ` Greg KH
2005-03-10 17:19 ` John Richard Moser
2005-03-10 17:24 ` Greg KH
2005-03-10 17:02 ` Ralf Baechle
2005-03-10 17:25 ` John Richard Moser
2005-03-10 17:24 ` John Richard Moser
2005-03-10 20:03 ` Diego Calleja
2005-03-10 20:14 ` John Richard Moser
2005-03-10 21:21 ` Lennart Sorensen
2005-03-10 21:42 ` John Richard Moser
2005-03-10 22:31 ` Lee Revell
2005-03-10 21:59 ` Peter Chubb
2005-03-10 22:32 ` John Richard Moser [this message]
2005-03-12 15:53 ` Felipe Alfaro Solana
2005-03-13 5:01 ` John Richard Moser
2005-03-13 7:17 ` Mike Galbraith
2005-03-10 22:45 ` Rik van Riel
2005-03-11 10:39 ` Ben Dooks
2005-03-11 16:39 ` Benedikt Spranger
2005-03-11 16:10 ` Jon Smirl
2005-03-11 9:33 ` [TROLL] " Xavier Bestel
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 4:57 Albert Cahalan
2005-03-19 11:29 ` Eric W. Biederman
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=4230CB07.3020904@comcast.net \
--to=nigelenki@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
/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.