Commits on Source (30)
-
Peter Hutterer authored
Fixes #137 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The previous check only worked if sizeof(long) > sizeof(int). Rather than be fancy about it, just cast to a signed long, check for negativity and continue based on that. Fixes #137 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
If sizeof(long) == sizeof(int), this test won't pass so let's drop it altogether. Fixes #137 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
-
Bennett Hardwick authored
-
Peter Hutterer authored
Was 0x800 in the hwdb, became 0x8000 in th quirks transition because of inflation, but let's pretend the economy is back to normal and devalue our currency. (aka: "it was a typo", whoops and whatnot) https://bugs.freedesktop.org/show_bug.cgi?id=104415 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Copy/paste typos introduced in the hwdb to quirks transition Fixes #141 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The hwdb match entry used to be this one: libinput:name:*Elan Touchpad*:dt:* LIBINPUT_ATTR_PRESSURE_RANGE=10:8 from commit 596777a3. It was intended to match for devicetree only but the way the udev rules were composed, it ended up matching on any system. Restore that for all systems to have compatibility with 1.11. For this one, let's also add the resolution hint and hope that that works too. Fixes #140 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Diego Rondini authored
Fix libinput_event_destroy call by passing the correct parameter (event) in the example code. Signed-off-by:
Diego Rondini <diego.rondini@kynetics.com>
-
Peter Hutterer authored
-
Peter Hutterer authored
-
Peter Hutterer authored
Anything that merely requires a once-off check during initialization can just use the quirks directly, no need to copy them over to the model flags. Fixes #146 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Reduces the places we need to update bits for new quirks. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Pretends to have a middle button where there is none. Fixes #142 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This touchpad stops sending pressure data after the first frame of the second finger down. If the initial pressure is too light, the finger doesn't get detected even when the pressure increases in the future. This thing is from 2014, so let's just disable the pressure axes on it and skip the pressure-based touch detection code. Let's hope that it doesn't also have ghost touches on light interactions... Fixes #145 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
This is a 0-360 ranged value, so let's print it aligned. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Because that's how we use it. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
When we disable the touch device, any existing touches should be cancelled, not just released. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
-
Peter Hutterer authored
Fixes #148 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
tp_detect_thumb_while_moving() assumes that of the 2 fingers down, at least one must be in TOUCH_UPDATE, otherwise we wouldn't have a speed to analyze for thumb. If a touch starts in HOVERING and exceeds the speed limit, we were previously increasing the 'exceeded count'. This later leads to an assert() in tp_detect_thumb_while_moving() when the second finger comes down because although we have multiple fingers, none of them are in TOUCH_UPDATE. This only happens when fingers 2 and 3 come down in the same event frame, because then we have nfingers_down at 2 (the hovering one doesn't count) but we don't yet have a finger in TOUCH_UPDATE. Fix this twofold, first by now calculating the speed on anything but TOUCH_UPDATE. And second by force-resetting the speed count on TOUCH_BEGIN/TOUCH_END so we definitely cover all the hover transitions. Fixes #150 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
We rely on the udev keyboard builtin to set the fuzz but that builtin isn't run during udevadm test. So running sudo udevadm test shows the LIBINPUT_FUZZ properties the first time round (still set from boot), but not the second time. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Timo Aaltonen authored
-
Timo Aaltonen authored
-
Timo Aaltonen authored
-
Timo Aaltonen authored
.gitlab/issue_templates/Bug.md
0 → 100644
.gitlab/issue_templates/FeatureRequest.md
0 → 100644
quirks/30-vendor-kensington.quirks
0 → 100644