From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kernel modules
Date: Mon, 10 Nov 2003 11:46:34 +0000 [thread overview]
Message-ID: <c64f2f65adf1da1d158700014ef6fc48@caldo.demon.co.uk> (raw)
In-Reply-To: <2b7b451e1182a260aa2887e810b907f4@plan9.escet.urjc.es>
dynamically-loaded modules are useful--perhaps even essential--
for some things, but most usb work still doesn't really require
kernel support for much more than managing the IO streams once the
device is configured. the interface to those streams
needs to be improved, partly because the spec was ambiguous
about one point, and partly because of experience with it,
but having looked at the usb support in other systems, i think
it's good to aim to keep it out of the kernel.
next prev parent reply other threads:[~2003-11-10 11:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 23:50 Fco.J.Ballesteros
2003-11-10 11:46 ` Charles Forsyth [this message]
2003-11-10 14:34 ` ron minnich
2003-11-10 14:38 ` Fco.J.Ballesteros
2003-11-10 14:44 ` ron minnich
2003-11-10 14:38 ` Sape Mullender
2003-11-10 14:41 ` Fco.J.Ballesteros
2003-11-10 14:46 ` ron minnich
2003-11-10 14:48 ` Sape Mullender
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=c64f2f65adf1da1d158700014ef6fc48@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).