Simon Geard wrote:
Ah, so for the evdev driver, the only config section you'd need would be
something like:
Section "InputDevice"
Identifier "Mouse0"
Driver "evdev"
Option "Device" "/dev/input/event0"
# Better use some udev rule to get a persistent name, and use this
# persistent name here. Also,
Option "CorePointer"
EndSection
and that's all. No protocol.
I'm wanting to get this clear, since I was able to find very little
documentation on evdev, and some of that quite misleadingly out of date
- e.g one source suggested keeping 'mouse' driver, but using 'evdev'
protocol.
I could verify that the setup above works with my regular Genius
NetScroll PS/2 mouse, and with my old serial mouse when I run the
"inputattach" program as follows:
inputattach -ms3 /dev/ttyS1
Unfortunately, I don't have fancy mice, thus I can't test if
ZAxisMapping is ever necessary with evdev. The wheel "just works".
--
Alexander E. Patrakov
Don't mail to [EMAIL PROTECTED]: the server is off until 2006-01-11
Use my GMail or linuxfromscratch address instead
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
