From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] usb keyboard & mouse
Date: Fri, 7 Nov 2003 10:55:30 -0500 [thread overview]
Message-ID: <5f15d6a56a3d27d541a8f2938a1db6c5@plan9.bell-labs.com> (raw)
In-Reply-To: <f82f91c868d4b7322a72dd140ea0212b@plan9.escet.urjc.es>
> The solutions I'm using are:
> I included two more programs, sic, into /boot: usb/usbd and usb/usbhid
> and made boot to try to start usbhid if feasible, so we could type.
>
> I added yet another file to devcons, sic, (kbdin) to supply keys to the
> kernel. Regarding this, to have different keyboard maps, sic, I had to
> include in usbhid the kbdmaps I want to use, since it's better to supply
> runes to the kernel, and not scan codes.
I think your solution is fine and the complexity is only avoidable by putting the usb
drivers into the kernel. Maybe we'll do that when we get loadable drivers, but now
I don't think that's a good idea.
Note that we already have kbdin on the bitsy.
Sape
prev parent reply other threads:[~2003-11-07 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 14:58 Fco.J.Ballesteros
2003-11-07 15:55 ` Sape Mullender [this message]
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=5f15d6a56a3d27d541a8f2938a1db6c5@plan9.bell-labs.com \
--to=sape@plan9.bell-labs.com \
--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).