From: matt@proweb.co.uk
To: 9fans@cse.psu.edu
Subject: [9fans] usbd
Date: Sun, 7 Mar 2004 01:45:53 +0000 [thread overview]
Message-ID: <658ff6241f2a6ef94ae94c88e2faab5c@juice.thebigchoice.com> (raw)
How does one begin to fiddle with USB?
From reading usb(3) I should have
/dev/usbm
but I don't
I've tried two different PCs with the same result
9% bind -a '#U' /dev
9% usb/usbd -dv
usbd: enumeration complete
9% ls /dev/usb*
ls: /dev/usb*: '/dev/usb*' file does not exist
Where am I going wrong?
usbsnoopy was pretty useless btw. it refreshes the window once per second which means you cant click fast enough to select a device and press install. It's a Visual Studio project and I don't have VC to re-compile it with a longer refresh. I found a shareware program that seems pretty good (30 days or 100 starts).
"Universal Serial Bus (USB) connects more than computers and peripherals. It has the power to connect you with a whole new world of PC experiences." - hmm
m
next reply other threads:[~2004-03-07 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 1:45 matt [this message]
2004-03-07 1:55 ` Geoff Collyer
2004-03-07 1:57 ` Geoff Collyer
2004-03-07 2:02 ` Geoff Collyer
2004-03-07 4:15 ` sape
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=658ff6241f2a6ef94ae94c88e2faab5c@juice.thebigchoice.com \
--to=matt@proweb.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).