1. 22 May, 2020 5 commits
  2. 21 May, 2020 2 commits
    • Peter Hutterer's avatar
      Deprecate wheel tilt as separate axis source · 4ff6d6e3
      Peter Hutterer authored
      This has never been supported through the stack. No device ever had the
      required MOUSE_WHEEL_TILT_VERTICAL/HORIZONTAL udev property set, so
      libinput never set the right axis source. Neither weston nor mutter
      added the code for it. Even if we added wheel tilt for devices now, it
      would break those devices. And the benefit we get from having those
      separate is miniscule at best.
      So let's do the long-term thing and just deprecate this axis source.
      The wheel tilt mouse test device remains in the test suite, with the
      udev properties set just to verify that we do indeed ignore those now.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
    • Peter Hutterer's avatar
      quirks: mark the 0x233 razer keyboard as internal · 152837f4
      Peter Hutterer authored
      Razer Blade 2018 has a different model ID than the one we already have.
      Fixes #489
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  3. 13 May, 2020 2 commits
    • Peter Hutterer's avatar
      evdev: warn if our event processing lags by 10ms or more · bd7b9106
      Peter Hutterer authored
      Take a snapshot of the time every 10 libinput_dispatch() calls. During event
      processing, check if the event timestamp is more than 10ms in the past and
      warn if it is. This should provide a warning to users when the compositor is
      too slow to processes events but events aren't coming in fast enough to
      trigger SYN_DROPPED.
      Because we check the device event time against the dispatch time we may get
      warnings for multiple devices on delayed processing. This is intended, it's
      good to know which devices were affected.
      In the test suite we need to ignore the warning though, since we compose the
      events in very specific ways it's common to exceed that threshold
      (particularly when calling litest_touch_move_to).
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
    • Peter Hutterer's avatar
      test: fix the lookup for the timer offset warnings · 2ff0c342
      Peter Hutterer authored
      This was changed in 5e25bdfb but the litest
      message lookup wasn't changed. Let's do that now and change to a generic
      wording we can re-use for other messages.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  4. 12 May, 2020 1 commit
  5. 08 May, 2020 1 commit
  6. 19 Apr, 2020 4 commits
  7. 18 Apr, 2020 1 commit
  8. 16 Apr, 2020 2 commits
  9. 11 Apr, 2020 7 commits
  10. 06 Apr, 2020 1 commit
  11. 04 Apr, 2020 1 commit
  12. 31 Mar, 2020 1 commit
    • Peter Hutterer's avatar
      tablet: use the AttrPressureRange quirk for tablets too · 72af32c8
      Peter Hutterer authored
      The Aiptek 8000U has a pressure offset above our default (%5) but no
      meaningful way of detecting that. It doesn't provide distance or BTN_TOOL_PEN
      either, so our heuristics can't hook onto anything. BTN_TOUCH is set by this
      tablet but not at consistent pressure thresholds.
      Work around this by shipping a quirk that ups it to 70. Aiptek
      re-uses USB IDs because of course they do, so this applies to more than one
      device. Let's see what breaks.
      Fixes #462
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  13. 30 Mar, 2020 5 commits
  14. 29 Mar, 2020 1 commit
  15. 25 Mar, 2020 2 commits
  16. 23 Mar, 2020 4 commits