Subject: Re: wscons input multiplexor
To: None <email@example.com>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Date: 07/22/1999 23:36:28
> I've added a multiplexor pseudo-device to wscons. [...]
Most of this I like.
The major thing I dislike is the "mux" (pseudo-)locator on wsmouse and
wskbd devices, because it has nothing to do with where the device
attaches, but rather what attaches to it. I'd much rather have a way
for userland to attach mice and keyboards to muxes (which I gather you
do have) and then a way to set up a daemon that gets kicked when a new
wsmouse or wskbd appears, so it can then add it - or not, as it
pleases, possibly even after interacting with the user on the existing
The major thing I see unaddressed is controlling the keybaord/mouse.
For example, on the Sun ports, beeping is done by sending a command to
the keybaord to make it beep. If the X server's "keyboard" is a mux,
what happens when it tells its keyboard to beep? How does the mux know
which of its device(s) to pass that command along to? Similar remarks
apply to autorepeat and keyboard LED settings.
Aside from those warts, I think this is Pretty Cool Stuff.
7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B