Bug 16041 - Multitouch support not available for Synaptics touchpads
Summary: Multitouch support not available for Synaptics touchpads
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-24 12:46 UTC by RussianNeuroMancer
Modified: 2011-05-01 04:36 UTC (History)
4 users (show)

See Also:
Kernel Version:
Tree: Mainline
Regression: No


Attachments

Description RussianNeuroMancer 2010-05-24 12:46:18 UTC
Multitouch support not work on Lenovo Y550 Laptop.

# evtest /dev/input/event11
Input driver version is 1.0.0
Input device ID: bus 0x11 vendor 0x2 product 0x7 version 0x1b1
Input device name: "SynPS/2 Synaptics TouchPad"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 272 (LeftBtn)
    Event code 273 (RightBtn)
    Event code 274 (MiddleBtn)
    Event code 325 (ToolFinger)
    Event code 330 (Touch)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value      1
      Min     1472
      Max     5472
    Event code 1 (Y)
      Value   5855
      Min     1408
      Max     4448
    Event code 24 (Pressure)
      Value      0
      Min        0
      Max      255
    Event code 28 (Tool Width)
      Value      0
      Min        0
      Max        0

Multi-touch work in Windows with original driver.

I file Xorg/Input/Synaptics bug, but they say it's kernel issue: https://bugs.freedesktop.org/show_bug.cgi?id=28167

What information I can provide to help solve this driver issue?
Comment 1 Dmitry Torokhov 2010-05-24 18:07:17 UTC
Unfortunately Synaptics is not willing to disclose their multitouch protocol yet, si you either have to wait or try to reverse-engineer the protocol yourself by observing behavior of Windows driver. Maybe try set up KVM and Windowes as a guest and pass-through PS/2 stream form the guest directly to the PS/2 port via serio_raw driver...
Comment 3 Henrik Rydberg 2011-03-30 08:06:24 UTC
Fixed in 2.6.38.

Note You need to log in before you can comment on or make changes to this bug.