From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <5f15d6a56a3d27d541a8f2938a1db6c5@plan9.bell-labs.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] usb keyboard & mouse From: Sape Mullender In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Fri, 7 Nov 2003 10:55:30 -0500 Topicbox-Message-UUID: 81272454-eacc-11e9-9e20-41e7f4b1d025 > 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