* [9fans] usb keyboard & mouse
@ 2003-11-07 14:58 Fco.J.Ballesteros
2003-11-07 15:55 ` Sape Mullender
0 siblings, 1 reply; 2+ messages in thread
From: Fco.J.Ballesteros @ 2003-11-07 14:58 UTC (permalink / raw)
To: 9fans
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [9fans] usb keyboard & mouse
2003-11-07 14:58 [9fans] usb keyboard & mouse Fco.J.Ballesteros
@ 2003-11-07 15:55 ` Sape Mullender
0 siblings, 0 replies; 2+ messages in thread
From: Sape Mullender @ 2003-11-07 15:55 UTC (permalink / raw)
To: 9fans
> 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-11-07 15:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-11-07 14:58 [9fans] usb keyboard & mouse Fco.J.Ballesteros
2003-11-07 15:55 ` Sape Mullender
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).