From: James S. <jsi...@ac...> - 2000-03-27 02:16:16
|
> I'm currently attempting to slap together an XFree4 driver for Vojtech's > interface in my spare time. I'm hoping that with it you'll be able to have > X use a different keyboard than the kernel. Or, have two different X's use > different keyboards, for multiseat purposes. This would be really nice. > As a matter of terminology, I think multiseat is a much better term for a > system where multiple people can sit down and have independant sessions. > Were as multihead could also be just somebody with a 3840x1024 desktop. > Both have their uses, and are /really/ neat, but we do need to tell the > ideas apart. Alright. > So, if the console interface were able to handle > this style of input events the whole mess could be handled from either > userland or in the kernel, perhaps with some sort of fallover. Right. > userland: "cat /dev/evdev0 > /dev/consoledev0" effectivly attaches evdev0 > to console0. Ugly, but functional. It should already be attached to the first console. I never liked the idea of mapping devices from one head to another. Fbdev does this and it has it problems. > As for that fallover, what I meant by that is, maybe, any device(s) not > explicitly claimed by anything else(any console) would just fall through to > a default. That way no configuration would need to be done in the > default/simplest case. ei: you let the smoke out of your AT/PS2 keyboard > port. No problem, just plug in a USB keyboard and everything is happy. Hot pluggable devices will be fun to deal with. For a fully functional console you want it to search for the one lacking that part and fill it in. > Then, of course, there is the biggest reason for considering Vojtech's > interface: It's allready in the kernel, via the USB code. Yep. "Look it's a text editor, no it's a OS, no it's Emacs" James Simmons ____/| fbdev/gfx developer \ o.O| http://www.linux-fbdev.org =(_)= http://linuxgfx.sourceforge.net U |