Re: Supporting multiple keyboard

[Vojtech P. <vo...@su...>]

On Sat, Jun 10, 2000 at 09:42:20AM -0400, James Simmons wrote:

> > If you plug in a PS/2 keyboard (and the i8042 kbd port is active,
> > there is going to be some changes to better support hot-plugging PS/2
> > keyboards and mice) then the atkbd.c module initializes it and registers
> > it with the input subsystem. evdev.c gets offered the input device, and
> > accepts it, because it accepts any input device. It creates
> > /dev/input/event0. keyboard.c doesn't get offered the device, because
> > it's not compiled in when ve don't have VT's.
> 
> I understand it now. What I was wondering was is thier a switch between
> data goingt to eventX or to the VT for the keyboard. If someone opens a
> eventX that is a keybaord and belongs to a VT will the data automaticallly
> flow to eventX instead of the console system.

The data always flows to both. Input.c is multiplexing it.

> > Btw, can this approach handle two displays with one keyboard?
> 
> I'm going to take heat for this but no. The reason being is linus is a
> strict about what things are defined as. Evstack attempted to bend the
> rules to what a tty was with multi keyboards and multiple displays. Linus
> did not like it. What will be accepted is a tty is one display and one
> keyboard. It also makes the design much simpler. Now I would like to see
> such features as well. So it accomplish this we need to make userland
> flexiable to be able to do this.

Uh-huh. This means we won't be able to do what we can do now - have a
VGA and a MDA adapters & displays and one keyboard and have some
consoles on the first and some on the other.

-- 
Vojtech Pavlik
SuSE Labs