Comment 15 for bug 403869

Revision history for this message
In , Peter Hutterer (peter-hutterer) wrote :

I just had a look at this again and the source of the whole issue is that the touchpad reports different coordinates that it provides. From the launchpad bugreport:

700-1100 no mouse movement
1100-5200 regular mouse movement
5200-5900 scrolling movement
5900-6250 no mouse movement

from the log:
(II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
(II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448

so anything above 5472 is iffy anyway. It also explains why a uinput test device is pointless here, uinput won't allow this stuff.

looking at the code, there's a few places where this could cause issues, especially when scaling back. However, I need feedback for a current version of synaptics, not 0.99.3 which the original bugreport is based on.

Is this still an issue with an up-to-date driver?