1. 15 Jul, 2020 4 commits
    • Peter Hutterer's avatar
      touchpad: disable jump detection on the Lenovo X1 Gen6 touchpad · ac91d8df
      Peter Hutterer authored
      This touchpad has firmware that seems to buffer events. In the words of the
        In usage, it feels like motions vary between smooth and choppy; slow
        movements are smooth and quick movements are choppy. It's as if the
        touchpad aggregates quick movements and sends one big movement instead
        of sending discrete events. To make the movement more natural, the
        events preceding the jump should be of higher magnitude and the jump
        less pronounced, but that's just not how the touchpad works, it seems.
      In the actual event data this looks exactly like a pointer jump: small
      movements, one big one, then small ones again. If we filter that large
      movement out we prevent the user from moving quickly.
      There's no way to detect this or work around this, so let's add a quirk that
      disables the jump detection for this device.
      Fixes #506Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
    • Peter Hutterer's avatar
    • Peter Hutterer's avatar
      evdev: drop the check for tablet vs joystick · b9ec4088
      Peter Hutterer authored
      libwacom has been unsetting ID_INPUT_JOYSTICK for known tablets since 2015
      (libwacom 0.12) so this comment is outdated. And the input-id udev builtin
      never labels something as tablet *and* joystick. Which means: systemd sets
      either tablet or joystick. For tablets that are known to libwacom the joystick
      bit gets corrected and we only see the tablet bits.
      Tablets unknown to libwacom remain as joysticks and are ignored but that's the
      behavior we had anyway.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
    • Peter Hutterer's avatar
      evdev: fix the check for tablet vs joystick · eededbeb
      Peter Hutterer authored
      A device may have ID_INPUT_JOYSTICK and ID_INPUT_KEY in which case it would
      still get added, despite being a joystick device. Make sure we check only the
      tablet and joystick bits - where a device has the joystick bit set but not the
      tablet one we ignore it.
      Note that this check will get removed in the next commit anyway, it's just
      here to make tracking the change easier in the history (and figuring out where
      potential regressions come from).
      Fixes #415Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  2. 14 Jul, 2020 2 commits
  3. 08 Jul, 2020 2 commits
  4. 07 Jul, 2020 6 commits
  5. 03 Jul, 2020 2 commits
    • Ryo Munakata's avatar
    • Peter Hutterer's avatar
      gitlab CI: hook up coverity · 04e61248
      Peter Hutterer authored
      This requires the COVERITY_SCAN_TOKEN as listed on the project settings page
      in coverity itself. The intention here is to run this as a scheduled job, with
      the pipeline schedule itself controlling the branch name etc. This way we can
      keep the gitlab CI simple enough and just check for COVERITY_SCAN_TOKEN
      This job shouldn't ever fail unless coverity is down (we'll fix that then),
      the results of the coverity run are sent to the user that owns the the
      scheduled pipeline, i.e. me.
      Because coverity does not currently work on F32 (invalid GNU version number:
      101), we force this to run on F31.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  6. 02 Jul, 2020 1 commit
  7. 01 Jul, 2020 2 commits
  8. 30 Jun, 2020 1 commit
  9. 25 Jun, 2020 1 commit
  10. 17 Jun, 2020 5 commits
  11. 15 Jun, 2020 2 commits
  12. 04 Jun, 2020 2 commits
  13. 03 Jun, 2020 8 commits
  14. 02 Jun, 2020 1 commit
  15. 27 May, 2020 1 commit