Brian S. Julin wrote: > On Wed, 28 Nov 2001 [EMAIL PROTECTED] wrote: > >>Well, now many people have kernel 2.4, and I'm thinking of giving the >>above plan a shot. >> > >>Anyone know what the the ____________ is? input-linux-mouse? >> > > GII can be used this way on any input that can be opened multiple > times -- if it cannot then X has the input handle and so GII cannot use > it (unless X is not told about the device, e.g. a second keyboard > or mouse.) Right now I think this limits it to the /dev/event input -- > X can be told to use /dev/input/* while GII uses the raw /dev/event handle. > Events appear on both of these handles, and the /dev/event handle > gets events from all of the devices while the /dev/input handles > get events from only one device. > > input-linux-evdev should work with USB mice/keyboards and with joysticks. > It will also work with ps2 mice/keyboards if you apply the input-ps2 > project's patch to the latest 2.4 series kernels. That's available > at http://www.transvirtual.com/~jsimmons/input-ps2.diff but may > require some minor Makefile massaging to get compiling.
Okay, just one more check before I leap into phun kernel recompile... My 2.4 box doesn't have /dev/event* yet. But it does have /dev/input/mice. If I use GII_INPUT="input-linux-mouse:imps2,/dev/mice", mhub seems to report buttons and mouse movement correctly, even under X11 (which also uses /dev/mice btw). This is with a USB wheelie mouse, haven't tried the ps2 yet. Is /dev/mice one of those inputs that can be opened multiple times? Is it low latency? ... I had not realized prior to your post that it was possible to have multiple keyboards/mice hooked up to a PC as game controllers. Neat!
