- Oct 10, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Oct 09, 2017
-
-
Peter Hutterer authored
The keyword is 'value', not 'default'. With meson 0.43 this now stops building. https://bugs.freedesktop.org/show_bug.cgi?id=103162 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This was accidentally made 755 as part of e9fc59ef Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
'rc' is possibly unused Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Oct 06, 2017
-
-
Peter Hutterer authored
When running with -j 1 and CK_FORK=no, the log_handler_count is shared between the tests. The log_priority tests can invoke the log handler during libinput_unref(), so on the next day the log handler starts with a nonzero log handler. Fix this by always initializing it to 0 in the tests we expect it to be zero and resetting it last. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 28, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 27, 2017
-
-
Peter Hutterer authored
These days it's mutter that controls the input devices, not g-s-d. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
exit code 77 signals "skip this test" Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 25, 2017
-
-
Peter Hutterer authored
Because on some devices the keyboard is where the fingers are holding the device when in tablet mode. https://bugs.freedesktop.org/show_bug.cgi?id=102729 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
if (foo) { everything } changed to : if (!foo) return everything Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Split out the fallback-specific device handling from the more generic evdev-specific handling (which is supposed to be available for all devices). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This is a fallback-specific private enum, don't pretend it's evdev-related Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Shove it into the generic dispatch interface so we don't entangle evdev and fallback. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Better for self-documentation than comments and makes it more obvious if we initialize something wrongly. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
-
Peter Hutterer authored
Previously we only listened for events on the first one to come up, based on the assumption that there can only be one internal keyboard. The Razer Blade laptop keyboards come with with multiple event nodes, all looking like a normal keyboard. The one that comes up first is one for special keys, so typing on the internal keyboard after a lid switch does not toggle the write state. Fix this by allowing for up to 3 keyboard listeners for a lid switch. https://bugs.freedesktop.org/show_bug.cgi?id=102039 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 21, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
All these tests were stored with "no device" as test name. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
All these tests were stored with "no device" as test name. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The test device initialization code was a bit of duplicated boilerplate and required adding a reference to the devices to the 'devices' list in litest.c. Automate this with a new TEST_DEVICE macro that adds the devices to a custom section in the binary, then loops throught that section to get the device out. This reduces the boilerplate for each test device to just the TEST_MACRO and the LITEST_foo device enum entry. It also now automates the shortname of the device. The device's shortname was standardised in this approach as well, lowercase and dashes only. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The ...create() method returned the wrong device, so this one was never actually used. Once we start using, we get test case failures related to the device having BTN_foo events as well. For now, just disable those codes so we have a keyboard with all keys and pass the tests. The rest needs better fixing. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Avoid processing an event with a time later than the earliest timer expiry. If libinput_dispatch() isn't called frequently enough, we may have e.g. a tap timeout happening but read a subsequent input event first. In that case we can erroneously trigger or miss out on taps, see wrong palm detection, etc. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
-
Peter Hutterer authored
And instead disable it when we do get a proximity out. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
-
- Sep 20, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
To get the new key defines Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
And remove an unnecessary one Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Obsolete since f0f63264 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 19, 2017
-
-
Peter Hutterer authored
Some devices like the UC Logic WP5540U has BTN_STYLUS but not BTN_TOOL_PEN. While a kernel bug, let's just handle these correctly anyway. https://bugs.freedesktop.org/show_bug.cgi?id=102570 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Yay-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
-
Peter Hutterer authored
Could be fixed in the kernel, but these tablets are effectively abandoned and fixing them is a one-by-one issue. Let's put the infrastructure in place to have this fixed once for this type of device and move on. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Yay-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 18, 2017
-
-
Peter Hutterer authored
evdev_log_* already writes the device name Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
A touchpad that was disabled by toggling the sendevents option would come back normally after a lid resume, despite still being nominally disabled. https://bugzilla.redhat.com/show_bug.cgi?id=1448962 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-