- Feb 02, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The timeout is too short, a number of users are unable to tap now. https://bugs.freedesktop.org/show_bug.cgi?id=99447 This reverts commit d0ba1e2b. (cherry picked from commit e86fdd58)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit ab563d09)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit a5cefb76)
-
Peter Hutterer authored
For each device open the various led devices (brightness only) and map the one nonzero brightness to the current mode. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit 5eb71b65)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit 9672e2f4)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit aae997e6)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit 13a2336b)
-
Peter Hutterer authored
Loop immediately exited, this code was never triggered. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit 4d20130e)
-
- Jan 19, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
When the filter code switched to raw device coordinates (bdd4264d) the input data remained in device coordinates. Since the factor for touchpads was still based on the physical velocity (and thus all touchpads get the same acceleration factor for identical moves), the actual delta was dependent on the resolution. e.g. touchpad with 40u/mm: delta of 2/2 * accel factor 2 -> accel delta of 4/4 touchpad with 20u/mm: delta of 1/1 * accel factor 2 -> accel delta of 2/2 The normalized coordinates should be independent of the touchpad's resolution though. Affected by this was the standard mouse accel code and the touchpad accel code, other filters always returned unnormalized coordinates (separate bug, not addressed here). This patch restores the correct behaviour for mice and touchpads while leaving the special filters untouched. For comparision: * 1000+dpi mice: accelerate normalized, return normalized * touchpads: accelerate unnormalized, return normalized * low-dpi mice: accelerate unnormalized, return unnormalized * trackpoints: accelerate unnormalized, return unnormalized * x230: don't touch, already does the right thing https://bugs.freedesktop.org/show_bug.cgi?id=99383 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Jan 18, 2017
-
-
Peter Hutterer authored
We were just switching type here without actual normalization, the filter code is in device units as of bdd4264d. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Jan 17, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Fallout from 5d66edc9 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Signed-off-by: Rohith Mukku <rohithmukku@gmail.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 16, 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>
-
Peter Hutterer authored
From systemd commit f644a6da7a: "pyparsing 2.1.10 fixed the handling of LineStart to really just apply to line starts and not ignore whitespace and comments any more. Adjust EMPTYLINE to this." Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Use the model names in the file name and append pad/pen/finger as appropriate Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
I'm using semaphore CI for build testing and that only provides Ubuntu 14.04 which doesn't have libevdev 1.3 or later. Since this is a minor workaround for an error case only, revert the commit again and leave the handling in. Less effort than having to patch around it in semaphore. This reverts commit 1e0736da.
-
- Jan 15, 2017
-
-
Peter Hutterer authored
gcov analysis showed that none of the actual testing conditions were hit, so the test succeeded despite not actually testing anything. Which is good, because testing for tilt normalization isn't correct anyway, tilt is in physical degrees, Drop the test and replace it with a test for pressure normalization instead. We already have a similar one to check for [0, 1] range, this new one explicitly tests for the extents. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This isn't true anymore with kernel 4.5 and libevdev 1.5.0 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
1.3 has been out since Sep 2014, that's enough time. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Don't access the struct until we've verified it is what we want. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
They weren't originally prefixed but the various tests were, but now that we only have one test runner binary anyway, the prefix helps sorting the files easily within e.g. gcov results. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
More consistency with udev-seat.(c|h) and no filename conflict with test/path. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 12, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Use the litest_assert_empty_queue() instead of manual checking, and remove the manual checks after the function call. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
These were just there so we didn't have an unused variable warning, but there's no reason even assigning to anything in the first place Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 11, 2017
-
-
Peter Hutterer authored
https://bugs.freedesktop.org/show_bug.cgi?id=99200 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
We used to mark dell touchpads this way but let's make this more generic. Nothing else used the dell touchpad model flag, so we can simply replace it. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 10, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Making sure the test suite behaves as expected should be done before we use it. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 04, 2017
-
-
Peter Hutterer authored
Only allow values of 0 and 1 for udev flags. Not that I'm aware of anyone using anything else (i.e. his shouldn't break anything) but it's best to be as restrictive as possible here. Bonus effect: it's now possible to unset LIBINPUT_MODEL_* tags as well, previously any value (including 0) was counted as "yes". Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Jan 03, 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>
-
Peter Hutterer authored
Also changes from W/H to WxH format Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 02, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-