From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] usbhid: usb keyboard/mouse
Date: Tue, 11 Nov 2003 16:46:24 +0100 [thread overview]
Message-ID: <b34fd588bfc87f36929d838a51fd55ea@plan9.escet.urjc.es> (raw)
I've pushed into sources /sys/src/cmd/usb/hid (under /nemo).
It's a usb keyboard / mouse usb driver with some keymaps.
I've been using it for some days with both keyboard&mouse,
and have tested it several times
with just a usb mouse. Although I consider it as beta and will
push (and let you know) a more stable version, I think it can
be used.
It uses the approach suggested by presotto, i.e. it mounts itself
at /dev supplying fake cons/consctl files. This means that
to use it at boot time you'd also need a change in /sys/src/9/boot/boot.c
to start both usbd and usbhid. (and also a change in /lib/namespace
to mount /srv/kfd (besides #c) for programs calling newns).
I'll post all the changes needed after doing more testing and
dismantling the `alternate keyboard driver' (keymaps are
now implemented within usbhid).
hth
reply other threads:[~2003-11-11 15:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b34fd588bfc87f36929d838a51fd55ea@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).