summaryrefslogtreecommitdiffstats
path: root/hwdb.d/70-mouse.hwdb (follow)
Commit message (Collapse)AuthorAgeFilesLines
* hwdb: add Kensington SlimBlade Pro trackball (Bluetooth mode)Celeste Liu2024-09-161-0/+4
| | | | | | | | | Wired and 2.4G dongle connectivity is covered by general trackball rule, but with Bluetooth connectivity Kensington SlimBlade Pro uses the name "SlimBlade Pro" which doesn't contain "[Tt]rack[Bb]all". We need to process it specially. Signed-off-by: Celeste Liu <CoelacanthusHex@gmail.com>
* 70-mouse.hwdb: Added Glorious Model O DPIRiku2024-07-071-0/+8
| | | This rule might also apply to the regular Model O (no minus), which has the same specifications.
* hwdb: Add Logitech MX Master 3S Bluetooth IDMaciej S. Szmigiero2024-05-311-1/+2
| | | | | | | | We already have an entry for this mouse when it is connected via USB Bolt receiver, now add a Bluetooth LE connection entry too. This mouse model supports both connection types, with up to 3 connection slots (to different hosts) per single mouse.
* hwdb: Add a Logitech MX Master 3S (connected via Bolt Receiver)Maciej S. Szmigiero2024-05-081-0/+4
| | | | | | | The mouse technically has settable DPI between 200 and 8000, with a step of 50, but 1000 DPI is the default setting. And if someone customizes the mouse DPI setting they can make a custom hwdb rule too.
* hwdb: Add a common Logitech M185/M225 mouse variantMaciej S. Szmigiero2024-04-281-0/+1
| | | | | Measured/tested on a Logitech N1901 mouse that apparently identifies as one.
* hwdb: Add Logitech G502 XMichael Kuhn2023-09-161-2/+6
| | | | | | | | The already existing entry refers to the Logitech G502 X LIGHTSPEED, rename it accordingly. DPI and frequency were taken from Logitech G HUB and https://www.logitech.com/assets/66240/2/g502-x-corded-gaming-mice-artanis.pdf
* Add alternate name for MX Ergo as found on some devicesRoger Gammans2023-07-131-0/+1
| | | | Fixes #28349
* hwdb: disable entry for Logitech USB receiver used by G502 XYu Watanabe2023-04-191-1/+3
| | | | | | Fixes a bug introduced by dede07d3d04007c70c78653a73e2bcd8616564a5. Fixes #27118.
* hwdb: Fixed thumb buttons reversed on CHERRY MW 2310 (#26992)taniishkaaa2023-03-261-0/+9
| | | Fixes #12914.
* hwdb: update 70-mouse.hwdb (#26782)tofylion2023-03-131-0/+6
| | | Add Logitech G502 X wired and wireless configurations with correct pid and vid.
* hwdb: drop boilerplate about match patterns being unstableZbigniew Jędrzejewski-Szmek2022-04-061-5/+0
| | | | | | | We've had this text since the beginning, but in fact the patterns must be stable in order for people to create local hwdb entries. And we support that and can't change the match patterns without being very careful. So let's just drop the text.
* hwdb: add CST Laser Trackball (#22583)prumian2022-02-221-0/+8
| | | Set the default to 800DPI as this is what user manual suggests.
* hwdb: add two Elecom trackballsRyan Hendrickson2022-01-281-0/+11
|
* hwdb: Add Kensington Expert Mouse Wireless TrackballTaiki Sugawara2021-11-151-0/+2
|
* Add Logitech USB-PS/2 M-BT96A to hwdbJohn Lindgren2021-09-221-0/+4
|
* hwdb: Add Logitech Trackman Marblemilaq2021-07-011-0/+4
| | | | As per Logitech specsheet and quick verification via mouse-dpi-tool
* hwdb: Use correct default values for Logitech M310milaq2021-07-011-1/+1
| | | | | | Altough the Logitech website states "1000 DPI", the default DPI settings seems to be 800 as shown by older versions of Logitech SetPoint and verification by mouse-dpi-tool.
* hwdb: Add Logitech G Pro Wirelessmilaq2021-07-011-0/+6
| | | | Use the default settings as advertised in the manual and in Logitech G HUB.
* hwdb: Add Logitech G700 "Nano" receivermilaq2021-07-011-0/+1
| | | | | | Although this mouse may be paired with other receivers this one is the "G-Series Nano Receiver" that originally shipped with the device.
* hwdb: Fix Logitech G700 default DPI settingsmilaq2021-07-011-1/+1
| | | | | | | The old settings were all over the place contained mixed refresh rates. The new settings are the correct default DPI settings as advertised online. This has also been confirmed in the latest Logitech Gaming Software (9.02.65).
* hwdb: Fix Logitech G500 default DPI settingsmilaq2021-07-011-1/+1
| | | | | These are the correct default DPI settings as advertised in the manual. This has also been confirmed in the latest Logitech Gaming Software (9.02.65).
* hwdb: Add DPI info for Logitech MX Ergomilaq2021-07-011-0/+1
| | | | | Use the "nominal value" as advertised in the spec sheet by Logitech. This has also been verified with mouse-dpi-tool.
* hwdb: Add Logitech G403 Heromilaq2021-07-011-0/+4
| | | | Use the default settings as advertised in the manual and in Logitech G HUB.
* Add Microsoft Pro Intellimouse MOUSE_DPI to hwdbSimon Watts2021-05-131-0/+4
| | | | | | - Internet specifications give 1600 DPI @ 1000Hz for this sensor - Confirmed experimentally via `mouse-dpi-tool` - vid, pid, and name match string from `mouse-dpi-tool`
* hwdb: unifying receiver match keys for Logitech MX ErgoDan Sanders2021-03-171-1/+3
|
* Add DPI info for Kensington Trackball Expert Mouse in hwdb (#18709)clayton craft2021-02-221-0/+1
| | | | The DPI value is from the manufacturer documentation, and freq measured from mouse-dpi-tool
* hwdb: Add Logitech MX 518 Legendary mousemoson-mo2021-01-181-0/+4
| | | Add Logitech MX 518 Legendary model to hwdb.
* hwdb.d/70-mouse.hwdb: add entry for ELECOM Huge TrackBallTad Fisher2021-01-121-0/+8
|
* Add Logitech G403 Prodigy Gaming Mouse to hwdb. (#17537)onlybugreports2020-11-101-0/+4
| | | | This PR adds logitech G403 to the hwdb. Settings were obtained with 'sudo mouse-dpi-tool /dev/input/event3' and 'ratbagctl hollering-marmot info'.
* hwdb: add trailing ":*" everywhereZbigniew Jędrzejewski-Szmek2020-10-151-123/+123
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | No functional change is intended. The general pattern of changes: -usb:v04F3p2B7C* +usb:v04F3p2B7C:* This is mostly a clarification, to make the part that makes the usb vXXXXpYYYY part visually separated. It would only make a difference if we added further keys with a different number of digits, which is unlikely. -usb:v0627p0001:*QEMU USB Keyboard* -usb:v0627p0001:*QEMU USB Mouse* -usb:v0627p0001:*QEMU USB Tablet* +usb:v0627p0001:*QEMU USB Keyboard*:* +usb:v0627p0001:*QEMU USB Mouse*:* +usb:v0627p0001:*QEMU USB Tablet*:* Again, only a clarification. We know that ":" will appear somewhere later in the match key, so anything that matches "…Keyboard*" will also match "…Keyboard*:*". -evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV* +evdev:name:ETPS/2 Elantech Touchpad:dmi:*svnASUSTeKComputerInc.:pnN53SV:* This makes the match narrower. Previously we would match product "N53SV" and "N53SV2", "N53SV3", and others. Here we are saying that the ':pn' part must match exactly. Most of the changes in this patch match this pattern. I made a few judgement calls and used "pn…*:*" when I wasn't sure if the full pn is included: -evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision* +evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*:* -evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*: +evdev:name:Cypress APA Trackpad ?cyapa?:dmi:*:svnHewlett-Packard*:pnFalco*:* This more like the "QEMU" example above, since all dmi strings end in ":", so anything which matches the old version will also match the new version. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:pvr* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnGateway*:pnA0A1*:* I replaced trailing ":pvr*" by ":*". This makes no functional difference because we expect "pvr" to always appear in the dmi string. This makes patterns shorter. -evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn* +evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:* OTOH, ":pn*" is kept. This is because almost patterns include ":pn*", and if we skip it, we should make it clear that this is on purpose, that we really want to match any product name. The python script to generate autosuspend rules is updated to use ":*" too. Inspired by https://github.com/systemd/systemd/pull/17281#discussion_r501489750.
* hwdb: reindent commments and say that "*" should always be trailingZbigniew Jędrzejewski-Szmek2020-10-151-20/+22
|
* hwdb: add another Logitech M705 mouse variantMaciej S. Szmigiero2020-07-061-0/+4
| | | | | | | There seems to be a newer version of Logitech M705 mouse in the wild. Let's add it to the hwdb. Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>
* hwdb: add another Logitech G502 Hero variant (#16256)Gigadoc22020-06-241-0/+2
| | | | The commit 67551ea already adds the G502 Hero mouse, but apparently there are multiple variants with the same ID but different names.
* hwdb: remove support for MOUSE_WHEEL_TILT_*Peter Hutterer2020-05-241-22/+0
| | | | | | | | | | | | | This has now been deprecated in libinput, the only known user of this property. It was never set for any device and weston and mutter, maybe other compositors, never added the code required to parse it. The benefit we could get in the UI from handling tilt differently to wheel is tiny and the lack of support shows that it isn't of interest to anyone. Let's remove this. See also https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/444
* Revert "Add Kensington SlimBlade Trackball"Zbigniew Jędrzejewski-Szmek2020-05-071-4/+0
| | | | This reverts commit 8049c79b654f9c00da883423813ec25b7b54f3d6.
* Add Zowie ZA12 details to mouse hwdbFerran Pallarès Roca2020-05-051-0/+6
|
* Add Kensington SlimBlade TrackballLukas Klingsbo2020-05-041-0/+4
|
* Add Logitech G502 HERO to mouse hwdbArthur Moraes do Lago2020-04-161-0/+2
|
* hwdb: Add Bluetooth-attached Logitech MX MasterJan Alexander Steffens (heftig)2019-12-171-1/+10
| | | | | Except for the product IDs, the original MX Master appears identical to the MX Master 2S.
* hwdb: trivial indentation fixLennart Poettering2019-12-111-3/+3
|
* Fix DPI for MX Master 2s bluetooth mouseRaphael2019-12-041-1/+1
| | | | Mouse behaviour is unusably slow disregardless of mouse speed settings.
* hwdb: Set trackball property for Logitech MX Ergo (#14231)xduugu2019-12-041-0/+4
|
* hwdb: add bluetooth entry for Logitech MX Anywhere 2SHaochen Tong2019-11-251-1/+5
|
* Rename udev's hwdb/ to hwdb.d/Zbigniew Jędrzejewski-Szmek2019-10-101-0/+739
As in the parent commit, this makes the name consistent with the rest of the source tree and the actuall installation path.