hwdb: add a new db for the DPI/frequency settings of mice
Pointer acceleration for relative input devices (mice, trackballs, etc.)
applies to the deltas of the device. Alas, those deltas have no physical
reference point - a delta of 10 may be caused by a large movement of a
low-dpi mouse or by a minute movement of a high-dpi mouse.
Which makes pointer acceleration a bit useless and high-dpi devices
essentially unusable.
In an ideal world, we could read the DPI from the device directly and work
with that. In the world we actually live in, we need to compile this list
manually. This patch introduces the database, with the usual match formats
and a single property to be set on a device: MOUSE_DPI
That is either a single value for most mice, or a list of values for mice
that can change resolution at runtime. The exact format is detailed in the
hwdb file.
Note that we're explicitly overshooting the requirements we have for
libinput atm. Frequency could be detected in software and we don't
actually use the list of multiple resolutions (because we can't detect
when they change anyway). However, we might as well collect those values
from the get-go, adding/modifying what will eventually amount to hundreds
of entries is a bit cumbersome.
Note: we rely on the input_id builtin to tag us as mouse first, ordering
of the rules is important.
(David: fixed up typos and moved hwdb file into ./hwdb/)
Signed-off-by: Anthony G. Basile <blueness@gentoo.org>
2014-11-25 18:35:16 +07:00
|
|
|
# do not edit this file, it will be overwritten on update
|
|
|
|
|
|
|
|
|
|
ACTION=="remove", GOTO="mouse_end"
|
|
|
|
|
KERNEL!="event*", GOTO="mouse_end"
|
|
|
|
|
ENV{ID_INPUT_MOUSE}=="", GOTO="mouse_end"
|
|
|
|
|
|
|
|
|
|
# mouse:<subsystem>:v<vid>p<pid>:name:<name>:*
|
|
|
|
|
KERNELS=="input*", ENV{ID_BUS}=="usb", \
|
|
|
|
|
IMPORT{builtin}="hwdb 'mouse:$env{ID_BUS}:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'", \
|
|
|
|
|
GOTO="mouse_end"
|
|
|
|
|
KERNELS=="input*", ENV{ID_BUS}=="bluetooth", \
|
|
|
|
|
IMPORT{builtin}="hwdb 'mouse:$env{ID_BUS}:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'", \
|
|
|
|
|
GOTO="mouse_end"
|
2014-12-23 07:14:19 +07:00
|
|
|
DRIVERS=="psmouse", SUBSYSTEMS=="serio", \
|
|
|
|
|
IMPORT{builtin}="hwdb 'mouse:ps2::name:$attr{device/name}:'", \
|
|
|
|
|
GOTO="mouse_end"
|
hwdb: add a new db for the DPI/frequency settings of mice
Pointer acceleration for relative input devices (mice, trackballs, etc.)
applies to the deltas of the device. Alas, those deltas have no physical
reference point - a delta of 10 may be caused by a large movement of a
low-dpi mouse or by a minute movement of a high-dpi mouse.
Which makes pointer acceleration a bit useless and high-dpi devices
essentially unusable.
In an ideal world, we could read the DPI from the device directly and work
with that. In the world we actually live in, we need to compile this list
manually. This patch introduces the database, with the usual match formats
and a single property to be set on a device: MOUSE_DPI
That is either a single value for most mice, or a list of values for mice
that can change resolution at runtime. The exact format is detailed in the
hwdb file.
Note that we're explicitly overshooting the requirements we have for
libinput atm. Frequency could be detected in software and we don't
actually use the list of multiple resolutions (because we can't detect
when they change anyway). However, we might as well collect those values
from the get-go, adding/modifying what will eventually amount to hundreds
of entries is a bit cumbersome.
Note: we rely on the input_id builtin to tag us as mouse first, ordering
of the rules is important.
(David: fixed up typos and moved hwdb file into ./hwdb/)
Signed-off-by: Anthony G. Basile <blueness@gentoo.org>
2014-11-25 18:35:16 +07:00
|
|
|
|
|
|
|
|
LABEL="mouse_end"
|