summaryrefslogtreecommitdiff
path: root/hwdb/70-mouse.hwdb
AgeCommit message (Collapse)Author
2015-01-09hwdb: add Kay's Laser Mouse to the dpi databaseLennart Poettering
2015-01-09hwdb: add missing line between the G400 entriesPeter Hutterer
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
2015-01-09hwdb: note that we care about the maximum frequency in MOUSE_DPIPeter Hutterer
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
2015-01-08hwdb: adjust max frequency of Logitech RX 250Zbigniew Jędrzejewski-Szmek
https://bugs.freedesktop.org/show_bug.cgi?id=87435
2015-01-07hwdb: mouse DPI data, Logitech Gaming Mouse G400Jonas Ådahl
2015-01-05hwdb: fix a typoPeter Hutterer
2015-01-05hwdb: revert Logitech Optical USB MousePeter Hutterer
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
2014-12-31hwdb: mouse DPI data, Logitech USB Laser Mouse M-U0011-OChristoph Brill
https://bugs.freedesktop.org/show_bug.cgi?id=87880
2014-12-30hwdb: mouse DPI data, Logitech M-UAS144Christoph Brill
https://bugs.freedesktop.org/show_bug.cgi?id=87881
2014-12-30hwdb: mouse DPI data, Fujitsu Siemens OEMChristoph Brill
https://bugs.freedesktop.org/show_bug.cgi?id=87879
2014-12-30hwdb: mouse DPI data, Logitech MK260 aka M-R0011Christoph Brill
https://bugs.freedesktop.org/show_bug.cgi?id=87882
2014-12-30hwdb: mouse DPI data, Chicony 2.4G Multimedia Wireless KitChristoph Brill
https://bugs.freedesktop.org/show_bug.cgi?id=87883
2014-12-26hwdb: mouse - add Razer AbyssusTom Gundersen
2014-12-24hwdb: add rule and first entry for PS/2 micePeter Hutterer
https://bugs.freedesktop.org/show_bug.cgi?id=87037
2014-12-24hwdb: Microsoft Wireless Laser Mouse 8000 DPI dataFrank Theile
https://bugs.freedesktop.org/show_bug.cgi?id=87587
2014-12-22hwdb: Lenovo USB mouse MO28UOL DPI dataFrank Theile
https://bugs.freedesktop.org/show_bug.cgi?id=87504
2014-12-18hwdb: move Logitech mouse to the right spotZbigniew Jędrzejewski-Szmek
2014-12-18hwdb: Logitech, Inc. RX 250 Optical Mouse DPI dataErik Auerswald
https://bugs.freedesktop.org/show_bug.cgi?id=87435
2014-12-18hwdb: Logitech, Inc. RX 300 Optical Mouse DPI dataTim JP
https://bugs.freedesktop.org/show_bug.cgi?id=87456
2014-12-16hwdb: Logitech MX1000, another Lenovo USB mousePeter Hutterer
Provided by Benjamin Bellec https://bugs.freedesktop.org/show_bug.cgi?id=87343
2014-12-16hwdb: more an entry for the MS Sculpt ErgonomicPeter Hutterer
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-15hwdb: fix orderingDaniel Mack
We sort by default DPI, not the first one in the list.
2014-12-15hwdb: Logitech G400sDaniel Mack
Provided by Peter Hutterer: https://bugs.freedesktop.org/show_bug.cgi?id=87332
2014-12-15hwdb: Logitech MX 518Harald Hoyer
2014-12-12hwdb: add more miceZbigniew Jędrzejewski-Szmek
https://bugs.freedesktop.org/show_bug.cgi?id=87271
2014-12-12hwdb: sort mice by brand,type,dpi,frequencyZbigniew Jędrzejewski-Szmek
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-10hwdb: fix typoTorstein Husebø
2014-12-10hwdb: add two more mice to the DPI databaseLennart Poettering
2014-12-10hwdb: add another Logitech mouse (M-BZ96C)Lennart Poettering
2014-12-10hwdb: add DPI data for M325 mouseLennart Poettering
2014-12-10hwdb: add more mouse DPI entriesPeter Hutterer
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-11-27hwdb: add a new db for the DPI/frequency settings of micePeter Hutterer
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/)
generated by cgit v1.2.3-54-g00ecf (git 2.45.2) at 2024-12-24 14:05:48 +0000