| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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>
|
|
|
| |
This rule might also apply to the regular Model O (no minus), which has the same specifications.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Measured/tested on a Logitech N1901 mouse that apparently identifies as
one.
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Fixes #28349
|
|
|
|
|
|
| |
Fixes a bug introduced by dede07d3d04007c70c78653a73e2bcd8616564a5.
Fixes #27118.
|
|
|
| |
Fixes #12914.
|
|
|
| |
Add Logitech G502 X wired and wireless configurations with correct pid and vid.
|
|
|
|
|
|
|
| |
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.
|
|
|
| |
Set the default to 800DPI as this is what user manual suggests.
|
| |
|
| |
|
| |
|
|
|
|
| |
As per Logitech specsheet and quick verification via mouse-dpi-tool
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Use the default settings as advertised in the manual and in Logitech G HUB.
|
|
|
|
|
|
| |
Although this mouse may be paired with other receivers
this one is the "G-Series Nano Receiver" that originally
shipped with the device.
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
| |
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).
|
|
|
|
|
| |
Use the "nominal value" as advertised in the spec sheet by Logitech.
This has also been verified with mouse-dpi-tool.
|
|
|
|
| |
Use the default settings as advertised in the manual and in Logitech G HUB.
|
|
|
|
|
|
| |
- 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`
|
| |
|
|
|
|
| |
The DPI value is from the manufacturer documentation, and freq measured
from mouse-dpi-tool
|
|
|
| |
Add Logitech MX 518 Legendary model to hwdb.
|
| |
|
|
|
|
| |
This PR adds logitech G403 to the hwdb.
Settings were obtained with 'sudo mouse-dpi-tool /dev/input/event3' and 'ratbagctl hollering-marmot info'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
The commit 67551ea already adds the G502 Hero mouse, but apparently
there are multiple variants with the same ID but different names.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
This reverts commit 8049c79b654f9c00da883423813ec25b7b54f3d6.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Except for the product IDs, the original MX Master appears identical to
the MX Master 2S.
|
| |
|
|
|
|
| |
Mouse behaviour is unusably slow disregardless of mouse speed settings.
|
| |
|
| |
|
|
As in the parent commit, this makes the name consistent with the
rest of the source tree and the actuall installation path.
|