cvs commit: src/sys/dev/vkbd vkbd.c vkbd_var.h src/sys/modules/vkbd Makefile

[Marcel Moolenaar]

On Tue, Nov 16, 2004 at 11:17:18AM -0800, Maksim Yevmenkin wrote:
> 
> > there is no chance that the BT device could be needed for DDB or
> > single-user mode then I guess that your driver is a good thing, though
> > the 'vkbd' name is a bit misleading since it really only applies to BT.
> > But if you're interested in working with Brooks on a more unified
> > abstraction, please don't let me stop you =-)
> 
> bluetooth keyboard definitely not needed in ddb and single mode (imo).

I very strongly disagree with this. In fact, it's this sentiment that
created the PS/2 vs USB keyboard problem for which we need a mux. We
need to treat a keyboard as a keyboard because a keyboard is a keyboard.
Some keyboards lend themselves more easily for low-level access due to
the primitive nature of how one talks to the keyboard, but I think it's
a mistake to treat a PS/2 keyboard different from any other keyboard
simply because the interface is primitive. It's much more productive to
try to get USB, Bluetooth and firefire to work as soon as possible
during boot so that devices there can be used as early as PS/2 or legacy
PC devices.

The world is changing and we have syscons(4) to show what happens if
you don't keep up and make a serious attempt at providing the right
abstractions and interfaces to account for the new world order.

Other than that. I think vkbd(4) can stay. Between no support and
partial or imperfect support, we might as well keep the imperfect
support until we're done perfecting things. With vkbd(4), one can
actually use bluetooth in the common case. I think that's a big win
on its own.

Just my take on this,

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel at xcllnt.net