hwdb: add HP Pavilion dm4 axis corrections https://bugs.freedesktop.org/show_bug.cgi?id=91615

hwdb: add Samsung 305V4A axis resolutions From https://bugzilla.redhat.com/show_bug.cgi?id=1294022

hwdb: add axis ranges and resolution for Dell Lattitude E6220 https://bugzilla.redhat.com/show_bug.cgi?id=1293576

hwdb: remove references to udevadm info /dev/input/event*

hwdb: add axis range corrections for Lenovo T510 From https://bugzilla.redhat.com/show_bug.cgi?id=1247958

hwdb: add Dell Inspiron N5040 touchpad corrections From https://bugzilla.redhat.com/show_bug.cgi?id=1275070

hwdb: sort the brand names alphabetically

hwdb: fix capitalization of product version for the Macbooks We need uppercase hex here. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

Update bugtracker address

hwdb: add resolution information for Dell Vostro 1510 touchpad Dell Vostro 1510, AlpsPS/2 ALPS GlidePoint touchpad. Relevant issue: #763

hwdb: add min/max/resolution override for Appletouch one-button touchpads Macbook2,1, late 2006 model. https://bugzilla.redhat.com/show_bug.cgi?id=1246651

hwdb: add resolution values for Asus K52JT touchpad https://bugs.freedesktop.org/show_bug.cgi?id=91364

hwdb: fix typo - "sort by by..." -> "sort by..."

hwdb: add Chromebook pixel (2015) resolution fix 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.

hwdb: add evdev entry for the Lenovo X230 series touchpad 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.

hwdb: set the resolution for a couple of bcm5974 touchpads 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>

udev: builtin-keyboard: add support for EVDEV_ABS_* 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.