From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] just checking ...
Date: Fri, 24 Mar 2006 17:41:40 +0000 [thread overview]
Message-ID: <cf4d7e0cd66138041744826f803527fb@terzarima.net> (raw)
In-Reply-To: <9394663c4db4f35f890ee19ac3e37a17@proxima.alt.za>
> Actually, no, I need to debug /sys/src/9/pc/devusb.c as it does not
> detect the device the way NetBSD does. Incidentally, its VID and DID
it isn't really involved, except to store the values and return
them when a status file is read. usbd does the enumeration etc.
and it tags the device with vendor and device IDs once it has
got them, by writing them in a control message ("class" i think)
to the usb device ctl file. that's why you needed the updated
usbd as well as the usb driver. you need the latter to implement
the message; you need the former to do the work.
{usb/usbd -v} will trace some of its actions.
the driver is not even involved much in root port detection:
even then it's just a matter of returning to usbd
values it reads from the port control registers.
that's partly because the things must be polled, and
that might as well be programmed at user level,
where one can use thread.h
next prev parent reply other threads:[~2006-03-24 17:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 22:53 Ronald G Minnich
2006-03-22 23:47 ` erik quanstrom
2006-03-22 23:51 ` Ronald G Minnich
2006-03-23 0:01 ` Steve Simon
2006-03-23 0:02 ` erik quanstrom
2006-03-23 0:03 ` erik quanstrom
2006-03-23 0:01 ` Ronald G Minnich
2006-03-23 0:21 ` jmk
2006-03-23 15:13 ` Ronald G Minnich
2006-03-23 8:54 ` Gabriel Diaz
2006-03-23 9:57 ` Christoph Lohmann
2006-03-23 18:55 ` lucio
2006-03-23 21:29 ` Charles Forsyth
2006-03-24 5:35 ` lucio
2006-03-23 22:55 ` Christoph Lohmann
2006-03-24 5:24 ` lucio
2006-03-24 5:38 ` lucio
2006-03-24 10:51 ` Christoph Lohmann
2006-03-24 11:03 ` Charles Forsyth
2006-03-24 11:07 ` Charles Forsyth
2006-03-24 18:47 ` lucio
2006-03-24 20:51 ` Christoph Lohmann
2006-03-25 13:18 ` lucio
2006-03-24 14:50 ` lucio
2006-03-24 17:41 ` Charles Forsyth [this message]
2006-03-24 18:35 ` lucio
2006-03-24 18:59 ` Charles Forsyth
2006-03-24 20:41 ` Christoph Lohmann
2006-03-25 13:17 ` lucio
2006-03-25 13:33 ` Russ Cox
2006-03-25 14:35 ` lucio
2006-03-25 14:56 ` Russ Cox
2006-03-25 17:07 ` lucio
2006-03-25 22:01 ` Christoph Lohmann
2006-03-26 19:45 ` lucio
2006-03-23 15:14 ` Ronald G Minnich
2006-03-23 16:57 ` Charles Forsyth
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=cf4d7e0cd66138041744826f803527fb@terzarima.net \
--to=forsyth@terzarima.net \
--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).