1. 05 Sep, 2014 5 commits
  2. 03 Sep, 2014 1 commit
    • Peter Hutterer's avatar
      eventcomm: ensure we're on the same clock as the server · 90d19302
      Peter Hutterer authored
      Default on evdev devices is CLOCK_REALTIME. If that clock falls behind the
      server's CLOCK_MONOTONIC, motion after a clickpad click may be delayed by the
      difference in the clocks.
      In detail:
      When the timer func is triggered, GetTimeInMillis() which is CLOCK_MONOTONIC,
      is stored as hwState->millis. The eventcomm backend uses struct
      input_event time (CLOCK_REALTIME).
      When we read events from the device, if the evdev time is less than the server
      time, the fix for (#48777) sets the current event time to hwState->millis.
      Until the evdev time overtakes that stored time, all events have the
      hwState->millis time.
      If during that time a clickpad triggers a physical click,
      clickpad_click_millis is set to hwState->millis + the ignore-motion timeout.
      Thus, all motion is ignored until the event time overtakes that stored
      The whole issue is further enhanced by us unconditionally setting the timer
      func if we get any events, which is a separate issue anyway.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: default avatarHans de Goede <hdegoede@redhat.com>
  3. 28 Aug, 2014 2 commits
  4. 14 Aug, 2014 1 commit
  5. 08 Aug, 2014 3 commits
  6. 20 May, 2014 1 commit
  7. 13 May, 2014 1 commit
  8. 30 Apr, 2014 4 commits
  9. 29 Apr, 2014 1 commit
  10. 22 Apr, 2014 2 commits
  11. 09 Apr, 2014 4 commits
  12. 23 Mar, 2014 1 commit
    • Peter Hutterer's avatar
      Disable GrabEventDevice by default · f1948e08
      Peter Hutterer authored
      This was required when we started supporting hotplugging to avoid duplicate
      events. These days the drawback of not being able to record events in the case
      of a bug is significant.
      Check the configuration source on init. If the device was hotplugged through a
      a server config backend, disable the grab. If the device was statically
      configured through an xorg.conf then leave the default grab enabled to avoid
      a duplicate device.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: default avatarHans de Goede <hdegoede@redhat.com>
  13. 17 Mar, 2014 2 commits
  14. 14 Mar, 2014 1 commit
  15. 13 Mar, 2014 2 commits
  16. 12 Mar, 2014 4 commits
  17. 11 Mar, 2014 5 commits