From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: usbd - revision (Was: [9fans] USB developments)
Date: Fri, 16 Jan 2004 08:34:15 +0100 [thread overview]
Message-ID: <d1982e5b6dc4742dbae26a2ff50e72e6@plan9.escet.urjc.es> (raw)
In-Reply-To: <20040115211012.K25947@cackle.proxima.alt.za>
>> i was broadly happy with the kernel/user split, and
>> the overall structure. the kernel device is essentially
>> an IO multiplexor and i think that's about right. the kernel doesn't
>> need to know about fancy hub trees or HID descriptors,
>> and that also seems good to me. (for mouse and keyboard there
>> are or were special boot-time modes one could use before usbd could run.)
>> (in fact, usbd could probably devise/check the USB IO schedule too.)
>>
> Enter Nemo. I'll leave him to comment, I'm just a poorly informed
> spectator.
Regarding the hid, there's nothing special. It works in a back-compat
mode (boot mode) while the system gets up, to allow you to type.
Roughly, when usb gets up, it assumes that the system can speak its
usb protocol and switches to it. The only special thing is that hid introduced
the need to start usbd and usbhid at boot(8) time, since you must
mount the new /dev/cons (fake) device before anyone opens it.
But regarding this discussion, it's just another regular usb driver.
next prev parent reply other threads:[~2004-01-16 7:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 6:16 [9fans] USB developments Lucio De Re
2004-01-15 8:23 ` Fco.J.Ballesteros
2004-01-15 8:42 ` Lucio De Re
2004-01-15 9:13 ` Fco.J.Ballesteros
2004-01-15 9:17 ` Fco.J.Ballesteros
2004-01-15 10:05 ` Lucio De Re
2004-01-15 10:23 ` Fco.J.Ballesteros
2004-01-15 13:02 ` Lucio De Re
2004-01-15 14:05 ` Richard Miller
2004-01-15 14:44 ` Lucio De Re
2004-01-15 14:56 ` Fco.J.Ballesteros
2004-01-15 15:20 ` Lucio De Re
2004-01-15 15:41 ` Fco.J.Ballesteros
2004-01-15 14:53 ` Fco.J.Ballesteros
2004-01-15 21:25 ` Dan Cross
2004-01-15 10:30 ` usbd - revision (Was: [9fans] USB developments) Lucio De Re
2004-01-15 10:46 ` Fco.J.Ballesteros
2004-01-15 11:47 ` Lucio De Re
2004-01-15 12:11 ` Charles Forsyth
2004-01-15 12:43 ` Lucio De Re
2004-01-15 18:01 ` C H Forsyth
2004-01-15 19:10 ` Lucio De Re
2004-01-15 20:24 ` Charles Forsyth
2004-01-15 21:00 ` Micah Stetson
2004-01-16 6:18 ` Lucio De Re
2004-01-16 7:34 ` Fco.J.Ballesteros [this message]
2004-01-16 7:38 ` Fco.J.Ballesteros
2004-01-16 7:59 ` Lucio De Re
2004-01-16 10:23 ` Bruce Ellis
2004-01-16 10:32 ` Lucio De Re
2004-01-16 10:39 ` boyd, rounin
2004-01-16 10:45 ` Richard Miller
2004-01-16 11:41 ` Bruce Ellis
2004-01-16 11:50 ` rog
2004-01-15 9:07 ` [9fans] USB developments Charles Forsyth
2004-01-15 9:18 ` Fco.J.Ballesteros
2004-01-15 10:39 ` Lucio De Re
2004-01-15 10:48 ` Richard Miller
2004-01-15 9:10 ` Richard Miller
2004-01-15 9:14 ` Fco.J.Ballesteros
2004-01-16 9:59 ` boyd, rounin
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=d1982e5b6dc4742dbae26a2ff50e72e6@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).