1. 01 Feb, 2009 3 commits
  2. 20 Dec, 2008 1 commit
  3. 14 Dec, 2008 3 commits
  4. 10 Dec, 2008 2 commits
  5. 04 Dec, 2008 1 commit
  6. 03 Dec, 2008 3 commits
  7. 26 Nov, 2008 2 commits
    • Batchty's avatar
      Stop two-finger scrolling if no finger is present. · bfb264ea
      Batchty authored
      
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@redhat.com>
      Signed-off-by: default avatarSimon Thum <eGore@gmx.de>
      Signed-off-by: Henrik Rydberg's avatarHenrik Rydberg <rydberg@euromail.se>
      (cherry picked from commit 13c93be3)
      bfb264ea
    • Batchty's avatar
      Ignore moves during tap processing if no finger is down. · 9c639523
      Batchty authored
      
      
      The Dell Inspiron 1520 with a Synaptics touchpad loves to send event like
      these after every finger release :
      
          time     x    y   z f  w  l r u d m     multi  gl gm gr gdx gdy
         1.563  3224 1625  57 1  5  0 0 0 0 0  00000000   0  0  0   0   0
         1.574  3251 1632  30 1  5  0 0 0 0 0  00000000   0  0  0   0   0
         1.584  3292 1673  10 1  5  0 0 0 0 0  00000000   0  0  0   0   0
         1.594     1 5855   3 2  5  0 0 0 0 0  00000000   0  0  0   0   0
         1.634     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
         1.746     1 5855   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
         1.897     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
      
      Most of the time these events are ignored by the driver, but sometimes it
      confuses two-finger scrolling and tap detection.
      
      For example, in this log, the first tap is recognized, the second isn't :
      
          time     x    y   z f  w  l r u d m     multi  gl gm gr gdx gdy
        11.597     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        11.678     1 5855   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
        11.688     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        11.709  3862 2406   8 1  5  0 0 0 0 0  00000000   0  0  0   0   0
        11.719  3851 2464  67 1  5  0 0 0 0 0  00000000   0  0  0   0   0
        11.729  3849 2407  35 1  4  0 0 0 0 0  00000000   0  0  0   0   0
        11.739  3858 2578   5 1  9  0 0 0 0 0  00000000   0  0  0   0   0
        11.749  3858 2578   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
        11.850     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        11.860     1 5855   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
        12.073     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        12.083     1 5855   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
        12.347     1 5855   4 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        12.357  3844 2381  56 1  4  0 0 0 0 0  00000000   0  0  0   0   0
        12.377  3848 2361  32 1  4  0 0 0 0 0  00000000   0  0  0   0   0
        12.388     1 5855   3 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        12.398     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
        12.408     1 5855   0 0  0  0 0 0 0 0  00000000   0  0  0   0   0
        12.428     1 5855   1 2  5  0 0 0 0 0  00000000   0  0  0   0   0
      
      The problem with the second tap is that the driver check if the movement from
      (3848,2361) to (1,5855) is over TapMaxMove before it checks for a finger release.
      So the driver considers it as a (short) finger move.
      Add the condition ''the finger is still present'' to the 'move' condition, so
      we ignore these moves..
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@redhat.com>
      Signed-off-by: default avatarSimon Thum <eGore@gmx.de>
      Signed-off-by: Henrik Rydberg's avatarHenrik Rydberg <rydberg@euromail.se>
      (cherry picked from commit 6cbdb0a1)
      9c639523
  8. 24 Nov, 2008 1 commit
  9. 14 Nov, 2008 1 commit
  10. 11 Nov, 2008 1 commit
  11. 05 Nov, 2008 1 commit
  12. 30 Oct, 2008 2 commits
  13. 28 Oct, 2008 1 commit
  14. 16 Oct, 2008 3 commits
  15. 13 Oct, 2008 2 commits
  16. 10 Oct, 2008 3 commits
  17. 09 Oct, 2008 3 commits
  18. 07 Oct, 2008 6 commits
  19. 03 Oct, 2008 1 commit
    • Magnus Kessler's avatar
      Remove repeater functionality. · 2e00158d
      Magnus Kessler authored
      
      
      Remove the repeater functionality completely from the synaptics touchpad
      driver. It is buggy in its current implementation and its usefulness is
      questionable.
      
      According to the INSTALL file, the repeater is there only for testing. In
      fact, if a supported device is found even a configured repeater fifo is
      automatically disabled. For most users the functionality is therefore
      irrelevant and can be confusing. If I understand the workings of the
      repeater correctly, a developer could instead just read the data directly
      from an unsupported device's character special file under /dev
      or /dev/input.
      
      With today's more dynamic device configuration possibilities via udev and
      hal it's also less likely that the synaptics driver would silently block
      another devices data, this situation being for what the repeater
      functionality seems to have been introduced in the past.
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@redhat.com>
      2e00158d