On Wed, Nov 21, 2012 at 10:48:05AM +0100, Kamil Jońca wrote: > > I have got something like: > http://www.amazon.co.uk/Perixx-PERIPAD-501-86x75x11mm-Industrial-Professional/dp/B001CX85I8 > > with lsusb it shows as: > --8<---------------cut here---------------start------------->8--- > Bus 001 Device 092: ID 099a:a002 Zippy Technology Corp. > --8<---------------cut here---------------end--------------->8--- > > Relevant xorg logs are > --8<---------------cut here---------------start------------->8--- > [1291767.832] (II) config/udev: Adding input device Mouse Pad > (/dev/input/mouse1) > [1291767.832] (**) Mouse Pad: Applying InputClass "mousepad" > [1291767.832] (II) No input driver specified, ignoring this device. > [1291767.832] (II) This device may have been added with another device file. > [1291767.837] (II) config/udev: Adding input device Mouse Pad > (/dev/input/event7) > [1291767.837] (**) Mouse Pad: Applying InputClass "evdev pointer catchall" > [1291767.837] (**) Mouse Pad: Applying InputClass "mousepad" > [1291767.837] (**) Mouse Pad: Applying InputClass "evdev pointer catchall" > [1291767.837] (II) Using input driver 'evdev' for 'Mouse Pad' > [1291767.837] (**) Mouse Pad: always reports core events > [1291767.837] (**) evdev: Mouse Pad: Device: "/dev/input/event7" > [1291767.837] (--) evdev: Mouse Pad: Vendor 0x99a Product 0xa002 > [1291767.837] (--) evdev: Mouse Pad: Found 3 mouse buttons > [1291767.837] (--) evdev: Mouse Pad: Found scroll wheel(s) > [1291767.837] (--) evdev: Mouse Pad: Found relative axes > [1291767.837] (--) evdev: Mouse Pad: Found x and y relative axes > [1291767.838] (II) evdev: Mouse Pad: Configuring as mouse > [1291767.838] (II) evdev: Mouse Pad: Adding scrollwheel support > [1291767.838] (**) Option "Emulate3Buttons" "on" > [1291767.838] (**) evdev: Mouse Pad: YAxisMapping: buttons 4 and 5 > [1291767.838] (**) evdev: Mouse Pad: EmulateWheelButton: 4, > EmulateWheelInertia: 10, EmulateWheelTimeout: 200 > [1291767.838] (**) Option "config_info" > "udev:/sys/devices/pci0000:00/0000:00:02.1/usb1/1-4/1-4.2/1-4.2:1.0/input/input70/event7" > [1291767.838] (II) XINPUT: Adding extended input device "Mouse Pad" (type: > MOUSE, id 8) > [1291767.838] (II) evdev: Mouse Pad: initialized for relative axes. > [1291767.838] (**) Mouse Pad: (accel) keeping acceleration scheme 1 > [1291767.838] (**) Mouse Pad: (accel) acceleration profile 0 > [1291767.839] (**) Mouse Pad: (accel) acceleration factor: 2.000 > [1291767.839] (**) Mouse Pad: (accel) acceleration threshold: 4 > --8<---------------cut here---------------end--------------->8--- > > > I added Input section for it: > > --8<---------------cut here---------------start------------->8--- > Section "InputClass" > Identifier "mousepad" > MatchProduct "Mouse Pad" > Option "Emulate3Buttons" "on" > EndSection > --8<---------------cut here---------------end--------------->8--- > > And now everything works fine except two things: > 1. Cannot disable tapping. I tried to use "synaptic" driver for this > device, but got only something like "cannot determine protocol".
if you look at the axis and buttons found, this device looks like a generic mouse with two relative axes, a scroll wheel and 3 buttons. most touchpads these days have this mode, and while in this mode they implement tapping, scrolling etc in the firmware. The solution here is to get the kernel to initialise the device into a raw mode, where we get the actual events from the touchpad and the features can be controlled by the X input module. > 2. How can I tune acceleration? xinput list-props, all properties prefixed with Device Accel Cheers, Peter _______________________________________________ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com