9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] usb keyboard & mouse
Date: Fri,  7 Nov 2003 15:58:28 +0100	[thread overview]
Message-ID: <f82f91c868d4b7322a72dd140ea0212b@plan9.escet.urjc.es> (raw)

Hi,
	I've implemented a usb/usbhid command along the lines of
usbmouse to use usb keyboards as well. However, I'm not happy with the
overall scheme, although I see no better way. This mail is just to ask
you for better ideas. In any case, once the thing has been in use for some days
I'll put it into sources. usb/usbhid handles both keyboard and mouse devices,
since they are often supplied by the same usb device.

The problems are:
	the keyboards are used by boot,
	and they must send keys to the kernel.

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.

In few words, my problem is that although I think I need all the bits in the keyboard
driver(s), it's already complex enough that I feel a better way must exist. Do you know
of such a way?

thanks

PS: I have as a requirement the ability to use different keymaps in the boot prompts
both for machines with usb keyboards and for machines with non-usb keyboards.




             reply	other threads:[~2003-11-07 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-07 14:58 Fco.J.Ballesteros [this message]
2003-11-07 15:55 ` Sape Mullender

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=f82f91c868d4b7322a72dd140ea0212b@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).