Age | Commit message (Collapse) | Author |
|
Update the location of the bug tracker and mention that pull requests
are preferred.
|
|
|
|
|
|
|
|
|
|
Since 3.19, the devices have the proper vid/pid and the model number in the
name.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
DPI is guesswork, no specs found on the web and calculating DPIs on a
trackball is tedious.
|
|
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=90540
|
|
http://www.logitech.com/en-us/product/wireless-trackball-m570#specs
https://bugzilla.redhat.com/show_bug.cgi?id=1217881
|
|
|
|
Device name is PixArt, but it's sold as a HP brand.
https://bugs.freedesktop.org/show_bug.cgi?id=90142
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=89743
|
|
|
|
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=89149
|
|
This device has 18 stops per rotation == 20 degree angle. Advertised as
"Micro-precise scrolling"
|
|
Most mice have a wheel click angle of 15 degrees, i.e. 24 clicks per full
wheel rotation. Some mice, like the Logitech M325 have a larger angle. To
allow userspace to make use of that knowledge, add a property to the hwdb.
This allows for better predictive scrolling. e.g. a mouse that has a smaller
click angle will scroll faster, with this value you can accommodate this
where needed. Likewise, using "half turn of the wheel" or "full turn of the
wheel" as a UI element becomes possible.
This addition is mainly driven by libinput 0.8, having the angle enables
libinput to provide an API that distinguishes between a physical distance
(like touchpad scrolling does) and discrete steps (wheel clicks).
Callers can choose what they prefer based on the device.
|
|
|
|
Error, DATA expected but got 'mouse:usb:v046dpc24c:name:Logitech G400s Optical
Gaming Mouse:' in '/etc/udev/hwdb.d/70-mouse.hwdb':
Error, MATCH expected but got ' MOUSE_DPI=400@1000 *800@1000 2000@1000
4000@1000' in '/etc/udev/hwdb.d/70-mouse.hwdb':
Introduced in 6366e349
|
|
Devices with dynamic frequency scaling adjust the frequency as needed. For
those we only care about the maximum frequency, not the various in betweens.
https://bugs.freedesktop.org/show_bug.cgi?id=87435#c8
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87435
|
|
|
|
|
|
Reporter says he incorrectly measured the data but the device is not available
anymore to correct it. We'll have to wait for someone else to submit the data.
https://bugs.freedesktop.org/show_bug.cgi?id=87343
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87880
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87881
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87879
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87882
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87883
|
|
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87037
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87587
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87504
|
|
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87435
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87456
|
|
Provided by Benjamin Bellec
https://bugs.freedesktop.org/show_bug.cgi?id=87343
|
|
Note that the MS receivers likely work like the Logitech ones, i.e. all
devices connected show up with the same vid/pid/name. Full evidence remains to
be gathered.
|
|
We sort by default DPI, not the first one in the list.
|
|
Provided by Peter Hutterer:
https://bugs.freedesktop.org/show_bug.cgi?id=87332
|
|
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=87271
|
|
This way entries from the same brand with the same dpi and frequency
can be coalesced. It is also visually easier to find the right DPI
than order hexadecimal identifiers.
|
|
|
|
|
|
|
|
|
|
Plus a note for Logitech devices using the unified receiver: these devices
include their wireless PID in the name, the usb PID/VID is the same for all.
In kernel 3.19 the actual model number will be the name, but the patches are
still a bit in flux at this point. In the future each device will need two
entries for pre+3.19 and 3.19.
https://bugs.freedesktop.org/show_bug.cgi?id=87037
https://bugs.freedesktop.org/show_bug.cgi?id=87072
https://bugs.freedesktop.org/show_bug.cgi?id=87162
|
|
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/)
|