1
1
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-23 17:34:00 +03:00
Commit Graph

72 Commits

Author SHA1 Message Date
Christoph Brill
149ff903ae hwdb: mouse DPI data, Logitech MK260 aka M-R0011
https://bugs.freedesktop.org/show_bug.cgi?id=87882
2014-12-30 18:56:16 -05:00
Christoph Brill
af157cf80b hwdb: mouse DPI data, Chicony 2.4G Multimedia Wireless Kit
https://bugs.freedesktop.org/show_bug.cgi?id=87883
2014-12-30 18:54:24 -05:00
Tom Gundersen
0068de375c hwdb: mouse - add Razer Abyssus 2014-12-26 00:28:05 +01:00
Peter Hutterer
60329a9d9f hwdb: add rule and first entry for PS/2 mice
https://bugs.freedesktop.org/show_bug.cgi?id=87037
2014-12-24 08:08:23 +10:00
Frank Theile
2c561af295 hwdb: Microsoft Wireless Laser Mouse 8000 DPI data
https://bugs.freedesktop.org/show_bug.cgi?id=87587
2014-12-24 08:08:20 +10:00
Frank Theile
c470b44ff0 hwdb: Lenovo USB mouse MO28UOL DPI data
https://bugs.freedesktop.org/show_bug.cgi?id=87504
2014-12-22 08:19:49 +10:00
Zbigniew Jędrzejewski-Szmek
f08fa3be8d hwdb: move Logitech mouse to the right spot 2014-12-18 18:54:01 -05:00
Erik Auerswald
90d37f7e8f hwdb: Logitech, Inc. RX 250 Optical Mouse DPI data
https://bugs.freedesktop.org/show_bug.cgi?id=87435
2014-12-18 18:54:00 -05:00
Tim JP
171347760e hwdb: Logitech, Inc. RX 300 Optical Mouse DPI data
https://bugs.freedesktop.org/show_bug.cgi?id=87456
2014-12-18 18:54:00 -05:00
Peter Hutterer
6a057a9985 hwdb: Logitech MX1000, another Lenovo USB mouse
Provided by Benjamin Bellec

https://bugs.freedesktop.org/show_bug.cgi?id=87343
2014-12-16 15:22:04 +10:00
Peter Hutterer
b631b4812a hwdb: more an entry for the MS Sculpt Ergonomic
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.
2014-12-16 15:20:25 +10:00
Daniel Mack
f9e35b2e0d hwdb: fix ordering
We sort by default DPI, not the first one in the list.
2014-12-15 17:15:16 +01:00
Daniel Mack
f8a9b6ae35 hwdb: Logitech G400s
Provided by Peter Hutterer:

  https://bugs.freedesktop.org/show_bug.cgi?id=87332
2014-12-15 17:11:31 +01:00
Harald Hoyer
de72f11bd1 hwdb: Logitech MX 518 2014-12-15 14:14:09 +01:00
Zbigniew Jędrzejewski-Szmek
e31fc1417a hwdb: add more mice
https://bugs.freedesktop.org/show_bug.cgi?id=87271
2014-12-12 18:20:51 -05:00
Zbigniew Jędrzejewski-Szmek
7731320a14 hwdb: sort mice by brand,type,dpi,frequency
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.
2014-12-12 18:17:37 -05:00
Torstein Husebø
8c67d0a74b hwdb: fix typo 2014-12-10 17:51:31 +01:00
Lennart Poettering
40dba7022a hwdb: add two more mice to the DPI database 2014-12-10 17:38:47 +01:00
Lennart Poettering
43db910dac hwdb: add another Logitech mouse (M-BZ96C) 2014-12-10 15:59:38 +01:00
Lennart Poettering
85c24db1f7 hwdb: add DPI data for M325 mouse 2014-12-10 15:46:08 +01:00
Peter Hutterer
eb59c75e9a hwdb: add more mouse DPI entries
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
2014-12-10 09:32:18 +10:00
Peter Hutterer
0213a26f65 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/)
2014-11-27 12:30:08 +01:00