Peter Hutterer 0e262e55bc evdev: reject devices with a min == max axis range ... Except for a few axes where this may be correct, a min == max axis range indicates a broken kernel driver. To avoid potential divisions by zero when scaling this axis later, reject such a device outright. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>		2015-03-23 14:24:27 +10:00
..
50-litest.conf
build-cxx.cc
build-pedantic.c
device.c	evdev: reject devices with a min == max axis range	2015-03-23 14:24:27 +10:00
keyboard.c
litest-alps-semi-mt.c
litest-bcm5974.c
litest-generic-singletouch.c
litest-int.h
litest-keyboard.c
litest-mouse.c
litest-ms-surface-cover.c
litest-protocol-a-touch-screen.c
litest-qemu-usb-tablet.c
litest-synaptics-hover.c
litest-synaptics-st.c
litest-synaptics-t440.c
litest-synaptics-x1-carbon-3rd.c
litest-synaptics.c	test: auto-update for BTN_TOOL_* when using litest_touch_ functions	2014-07-23 15:08:15 +10:00
litest-trackpoint.c
litest-vmware-virtual-usb-mouse.c
litest-wacom-intuos-finger.c
litest-wacom-touch.c
litest-xen-virtual-pointer.c
litest.c
litest.h
log.c
Makefile.am
misc.c
path.c
pointer.c
symbols-leak-test.in
touch.c
touchpad.c
trackpoint.c
udev.c
valgrind.suppressions