xf86-input-synaptics:synaptics-1.7-branch: 5 commit(s)

[Peter Hutterer]

Reporting from xf86-input-synaptics: xf86-input-synaptics driver

Please visit:
    http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics
Or get your own copy by using:
    git-clone git://anongit.freedesktop.org/xorg/driver/xf86-input-synaptics

5 commits against synaptics-1.7-branch at 7d958088...:
 configure.ac       |    2 +-
 src/eventcomm.c    |   13 +++++++++++--
 src/synaptics.c    |   51 ++++++++++++++++++++++++++++++++++++++++++++++++++-
 src/synapticsstr.h |    2 ++
 4 files changed, 64 insertions(+), 4 deletions(-)


commit d3331b5802602c059e311cffb17e4a18d4ae93f4
Author: Peter Hutterer <peter.hutterer at who-t.net>
Date:   Mon Dec 22 08:54:39 2014 +1000

    synaptics 1.7.7
    
    Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>

diffstat:
    configure.ac |    2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

cgit url:
http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?id=d3331b58


commit c3c68e3cbb04f869d075adaba5fa7fa2ef85a9d8
Author: Peter Hutterer <peter.hutterer at who-t.net>
Date:   Tue Sep 16 08:52:56 2014 +1000

    Limit the movement to 20 mm per event
    
    Touchpads are limited by a fixed sampling rate (usually 80Hz). Some finger
    changes may happen too fast for this sampling rate, resulting in two distinct
    event sequences:
    * finger 1 up and finger 2 down in the same EV_SYN frame. Synaptics sees one
      finger down before and after and the changed coordinates
    * finger 1 up and finger 2 down _between_ two EV_SYN frames. Synaptics sees one
      touchpoint move from f1 position to f2 position.
    
    That move causes a large cursor jump. The former could be solved (with
    difficulty) by adding fake EV_SYN handling after releasing touchpoints but
    that won't fix the latter case.
    
    So as a solution for now limit the finger movement to 20mm per event.
    Tests on a T440 and an x220 showed that this is just above what a reasonable
    finger movement would trigger. If a movement is greater than that limit, reset
    it to 0/0.
    
    On devices without resolution, use 0.25 of the touchpad's diagonal instead.
    
    Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>
    Reviewed-by: Hans de Goede <hdegoede at redhat.com>
    (cherry picked from commit 41b2312c006fca1f24e1a366174d3203a63fa04a)

diffstat:
    src/synaptics.c    |   33 +++++++++++++++++++++++++++++++++
    src/synapticsstr.h |    2 ++
    2 files changed, 35 insertions(+)

cgit url:
http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?id=d3331b58


commit c3df19df672754a950b66de53bcce0a1d898e7bf
Author: Peter Hutterer <peter.hutterer at who-t.net>
Date:   Tue Sep 16 10:44:40 2014 +1000

    Prohibit negative or zero x/y resolutions
    
    Default resolution is 1, don't allow setting 0 to avoid divisions by 0 or
    just general weirdness.
    
    Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>
    (cherry picked from commit 049611bd7f04e285909c55807478306cce83385f)

diffstat:
    src/synaptics.c |   10 ++++++++++
    1 file changed, 10 insertions(+)

cgit url:
http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?id=d3331b58


commit ffd51448fb484edaa08adb41b42f8adbab4c5457
Author: Peter Hutterer <peter.hutterer at who-t.net>
Date:   Fri Sep 5 15:14:47 2014 +1000

    When resetting, reset the open slots to -1
    
    open_slots holds the slot index, resetting it to 0 is a bad idea. And make
    sure that we do reset after DEVICE_INIT. We already do so on DEVICE_CLOSE, but
    after the first DEVICE_ON the data could still be random.
    
    Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>
    Reviewed-by: Keith Packard <keithp at keithp.com>
    (cherry picked from commit afbbcfa10eb3a2295823720907f35bb59972dd82)

diffstat:
    src/synaptics.c |    8 +++++++-
    1 file changed, 7 insertions(+), 1 deletion(-)

cgit url:
http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?id=d3331b58


commit fbf8df16694dd60d854f05f1f59a786c3df3529a
Author: Peter Hutterer <peter.hutterer at who-t.net>
Date:   Fri Sep 5 14:24:29 2014 +1000

    eventcomm: add missing axis labels to avoid array overrun
    
    And warn when we run out of labels.
    
    Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>
    Reviewed-by: Keith Packard <keithp at keithp.com>
    (cherry picked from commit d239f831f17ccf5468f5dc6b2f199a9c1f6e35af)
    
    Conflicts:
    	src/eventcomm.c

diffstat:
    src/eventcomm.c |   13 +++++++++++--
    1 file changed, 11 insertions(+), 2 deletions(-)

cgit url:
http://cgit.freedesktop.org/xorg/driver/xf86-input-synaptics/commit/?id=d3331b58