From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: [9fans] usb keyboard (usbhid)
Date: Mon, 22 Mar 2004 12:17:19 +0100 [thread overview]
Message-ID: <37495865411229f6d3bf5edee7becfac@plan9.escet.urjc.es> (raw)
This program changed one more time. I hope
it's the last time it happens.
I changed it to send scan codes from the usb keyboard
to the kernel. After considering all the alternatives,
the more simple and clean way was to remove all keymap
processing from usbhid and let the kernel do that (now that
the std one does it).
Thus, the usbhid thing stands now as follows:
- the usr-level program handles usb mouse/kbd.
- it feeds mouse / keyboard events through /dev files
- a pc/devkbdin.c provides /dev/kbdin for that purpose
- keymap, Latin composition, etc. are all handled by the kernel
using devkbmap.
I have pushed the changes to /n/sources/nemo.
hth
reply other threads:[~2004-03-22 11:17 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=37495865411229f6d3bf5edee7becfac@plan9.escet.urjc.es \
--to=nemo@lsub.org \
--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).