From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <f82f91c868d4b7322a72dd140ea0212b@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] usb keyboard & mouse
Date: Fri,  7 Nov 2003 15:58:28 +0100
Topicbox-Message-UUID: 81217dba-eacc-11e9-9e20-41e7f4b1d025

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.