Re: Supporting multiple keyboard

[James S. <jsi...@ac...>]

> > 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.

Hum?? This could be the way to handle the security problems with /dev/eventX 
and /dev/tty. On implict opening of /dev/event the data flows to the event
interface instead of to /dev/tty. Otherwise all data flows to /dev/tty. If
you need to send key events to the console while having /dev/event open 
then a program could send the data to /dev/tty directly. 

> 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.

You still can. Its just userland will handle this. A daemon could easily 
be created to handle this. The handling of odd ball systems with X amount
of keyboards and Y amount of video display systems where X != Y will get
very complex and very large. We are better off letting a userland app
handle this.

Q: Why did they deprecate a.out support in linux?
A: Because a nasty coff is bad for your elf.

James Simmons  [jsi...@li...]               ____/| 
fbdev/console/gfx developer                             \ o.O| 
http://www.linux-fbdev.org                               =(_)= 
http://linuxgfx.sourceforge.net                            U
http://linuxconsole.sourceforge.net