On Thu, 2005-06-30 at 15:32 +0100, Declan Moriarty wrote: > So I need /dev/input/mouse0, /dev/input/mouse1, etc. Can you show me a > 'ls -l' of your /dev/input please? The bootscripts don't seem to make > this stuff, so I'll do it by hand
delgarde:~$ ls -l /dev/input/* crw-r--r-- 1 root root 13, 63 2005-07-01 20:07 /dev/input/mice crw-r--r-- 1 root root 13, 32 2005-07-01 20:07 /dev/input/mouse0 crw-r--r-- 1 root root 13, 33 2005-07-01 20:07 /dev/input/mouse1 Those are populated by udev... one will be the usb mouse and the other the ps/2 trackball, but I've no idea which is which and it doesn't really matter. X just points at 'mice'. > This is interesting. I have just built 2.6.12.1, and have not got the > serial mouse enabled, and X works with this serial mouse. But that > option (Serial mouse) is not enabled or modularised :-o. Which interface is X using to see the mouse? If it's talking to the serial port directly (/dev/tts/0, or whatever), then kernel support for serial mice isn't applicable. The option above appears to be to allow the kernel to handle such a mouse through the input framework so that clients like X and GPM don't need to know what interface the physical device uses. For now though, they still support talking directly to serial mice, even if it means they need to be told which protocol the device speaks (harkening back to the days where every mouse needed it's own proprietary driver). Simon.
signature.asc
Description: This is a digitally signed message part
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
