1. 09 Oct, 2017 1 commit
  2. 25 Sep, 2017 9 commits
  3. 21 Sep, 2017 2 commits
  4. 20 Sep, 2017 4 commits
  5. 19 Sep, 2017 2 commits
  6. 18 Sep, 2017 2 commits
  7. 13 Sep, 2017 1 commit
  8. 10 Sep, 2017 1 commit
  9. 06 Sep, 2017 2 commits
  10. 05 Sep, 2017 5 commits
  11. 04 Sep, 2017 2 commits
  12. 01 Sep, 2017 3 commits
  13. 27 Aug, 2017 1 commit
  14. 23 Aug, 2017 1 commit
    • Peter Hutterer's avatar
      Add support for LIBINPUT_IGNORE_DEVICE · 00272cfb
      Peter Hutterer authored
      The recommended way to have libinput ignore specific devices so far was to
      remove the ID_INPUT* properties from the device. That may also affect other
      pieces of the stack that need access to this device.
      For the niche case of a device that should only be ignored by libinput but
      otherwise be treated normally by the system, we now support the
      If the property is set to "0", it's equivalent to being unset. This gets
      around some technical limitations in udev where unsetting a property is
      impossible via a hwdb entry.
      https://bugs.freedesktop.org/show_bug.cgi?id=102229Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  15. 14 Aug, 2017 1 commit
  16. 04 Aug, 2017 1 commit
  17. 01 Aug, 2017 2 commits
    • Hans de Goede's avatar
      touchpad: Enable timestamp smoothing support for bluetooth touchpads · c4857f01
      Hans de Goede authored
      Bluetooth wreaks havoc with the timestamp of the input events coming
      from the touchpad, enable timestamp smoothing support to counter this.
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
    • Hans de Goede's avatar
      filter: Add timestamp smoothing support · 6f39a9e1
      Hans de Goede authored
      Some devices, specifically some bluetooth touchpads generate quite
      unreliable timestamps for their events. The problem seems to be that
      (some of) these touchpads sample at aprox 90 Hz, but the bluetooth stack
      only communicates about every 30 ms (*) and then sends mutiple HID input
      reports in one batch.
      This results in 2-4 packets / SYNs every 30 ms. With timestamps really
      close together. The finger coordinate deltas in these packets change by
      aprox. the same amount between each packet when moving a finger at
      constant speed. But the time deltas are e.g. 28 ms, 1 ms, 1 ms resulting
      in calculate_tracker_velocity returning vastly different speeds for the
      1st and 2nd packet, which in turn results in very "jerky" mouse pointer
      *) Maybe it is waiting for a transmit time slot or some such.
      This commit adds support for a real simple timestamp smoothing algorithm,
      intended *only* for use with touchpads. Since touchpads will send a
      contineous stream of events at their sample rate when a finger is down,
      this filter simply assumes that any events which are under
      event_delta_smooth_threshold us apart are part of a smooth continuous
      stream of events with each event being event_delta_smooth_value us apart.
      Theoritically a very still finger may send the exact same coordinates
      and pressure twice, but even if this happens that is not a problem because
      a still finger generates coordinates changes below the hyst treshold so
      we ignore it anyways.
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>