| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=91615
|
|
From https://bugzilla.redhat.com/show_bug.cgi?id=1294022
|
|
hwdb: remove references to udevadm info /dev/input/event*
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=1293576
|
|
|
|
From https://bugzilla.redhat.com/show_bug.cgi?id=1247958
|
|
From https://bugzilla.redhat.com/show_bug.cgi?id=1275070
|
|
|
|
We need uppercase hex here.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
|
|
Dell Vostro 1510, AlpsPS/2 ALPS GlidePoint touchpad.
Relevant issue: #763
|
|
Macbook2,1, late 2006 model.
https://bugzilla.redhat.com/show_bug.cgi?id=1246651
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=91364
|
|
|
|
The atmel driver sets a default resolution of 20 for each touchpads it
creates. On this model, 10 is more appropriate.
The resolution is not set for the touchscreen by the kernel, so match
the name to both touchpad and touchscreen.
|
|
The Lenovo X230 advertize a vertical resolution of 136, which gives a true
size of 31 mm. The actual physical size of the touchpad is 40 mm, so
override the resolution to 100.
|
|
Verified for the 5,1 Macbook, the others are guesses based on the list of
supported devices of the moshi trackpad protector.
http://www.moshi.com/trackpad-protector-trackguard-macbook-pro#silver
Resolution calculated based on the min/max settings set in the kernel driver,
divided by the physical size. This is probably slightly off, but still better
than no resolution at all.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Parse properties in the form
EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>"
and apply them to the kernel device. Future processes that open that device
will see the updated EV_ABS range.
This is particularly useful for touchpads that don't provide a resolution in
the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974).
All values in the property are optional, e.g. a string of "::45" is valid to
set the resolution to 45.
The order intentionally orders resolution before fuzz and flat despite it
being the last element in the absinfo struct. The use-case for setting
fuzz/flat is almost non-existent, resolution is probably the most common case
we'll need.
To avoid multiple hwdb invocations for the same device, replace the
hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules
file. The new 60-evdev.rules is called for all event nodes
anyway, we don't need a separate rules file and second callout to the hwdb
builtin.
|
