delta/libevdev.git/tools, branch libevdev-1.8.0

Update struct input_event

2018-04-12T05:23:22+00:00

The struct input_event is not y2038 safe.
Update the struct according to the kernel patch:
https://lkml.org/lkml/2018/1/6/324

Signed-off-by: Deepa Dinamani 
Reviewed-by: Peter Hutterer 
Signed-off-by: Peter Hutterer

tools: add a script to sync the kernel header files

2017-07-03T00:13:40+00:00

Signed-off-by: Peter Hutterer

tools: print an error if we don't have any matching events in the dpi tool

2017-01-17T04:50:29+00:00

Beats crashing by dereferencing a null-pointer (when we access
m->frequencies[idx])

Signed-off-by: Peter Hutterer 
Reviewed-by: Benjamin Tissoires

tools: move udev printf into the print_summary() helper

2017-01-17T04:42:13+00:00

No functional changes

Signed-off-by: Peter Hutterer 
Reviewed-by: Benjamin Tissoires

tools: print the mean frequency together with the max frequency

2016-09-21T06:57:29+00:00

And if they're 30% out, print a warning. On the ThinkPad X1 Wireless Touch
Mouse (when connected via bluetooth) we get a bunch of events at the start of
the movement, all less than 1ms apart. Best guess is that the device goes to
low-power, then notices the movement and buffers the event until the BT
connection is back up. Then it sends all events at once. Usually they're less
than 1ms apart, but at one recording showed a 37ms delay before we go back to
the normal 70ms (~15Hz) the mouse has otherwise.

This is unpredictable enough that we can't just work around it so instead
print a warning to the user so they can go investigate.

https://bugs.freedesktop.org/show_bug.cgi?id=97812

Signed-off-by: Peter Hutterer 
Acked-by: Benjamin Tissoires

tools: rename frequency to max_frequency in the dpi tool

2016-09-19T00:55:51+00:00

Signed-off-by: Peter Hutterer

tools: use uint64_t, not doubles for the µs parameters

2016-09-15T21:26:42+00:00

Signed-off-by: Peter Hutterer

tools: fix kernel-announced width/height

2016-09-15T01:57:52+00:00

Side-effect of 240ba34ebd483 was that "touchpad size as listed by the kernel"
was now dependent on the values we got. This one is a static one based on the
axis info.

Signed-off-by: Peter Hutterer

tools: fix the touchpad resolution calculation

2016-08-26T01:43:54+00:00

Previous ones used the absinfo from the kernel but since we never updated that
from within the tool, the output was always the same.

Signed-off-by: Peter Hutterer

tools: require a minimum size for touchpads

2016-07-31T21:47:46+00:00

This mostly aims to catch users trying to specify the size in inches.

Signed-off-by: Peter Hutterer