Age | Commit message (Collapse) | Author |
|
Add hwdb parser to check for inconsistencies
|
|
|
|
Quoting https://github.com/systemd/systemd/pull/3906#discussion_r73828368:
> According to
> http://support.logitech.com/en_us/product/v220-cordless-optical-mouse-for-notebooks
> it seems the mouse is using a pre-version of the small unifying receiver we
> know now. If there are 2 mice with the same receiver, that means that the
> values should both be dropped IMO.
|
|
|
|
Whether a device is a trackball or not is a physical property so we should
store this globally, in one place. The new property must be set in addition to
ID_INPUT_MOUSE, otherwise existing clients won't detect the device.
No actual code changes required, the default match rule is simply checking for
"Trackball" in the name (in a few versions), other entries need to be added
manually.
|
|
Likely bad measurement and all other websites refer to it being 1000dpi.
See https://bugs.freedesktop.org/show_bug.cgi?id=96225#c13
This reverts commit e7b90ddc345d1817ca48bfcc4e3e73836c8051af.
|
|
https://bugs.freedesktop.org/show_bug.cgi?id=96225
and specifically the tech specs here:
http://support.logitech.com/en_us/product/corded-mouse-m500
|
|
|
|
Fixes #3009
|
|
hwdb: Add MODECOM MC-WM4 and Sharkoon Shark Force
|
|
|
|
|
|
hwdb: remove references to udevadm info /dev/input/event*
|
|
http://www.logitech.com/en-gb/product/corded-mouse-m500
|
|
|
|
[zj: rearrange into the sort order]
|
|
|
|
Fix typo in DPI: 32000 -> 3200
|
|
Remove whitespace from empty line in hwdb.
|
|
|
|
|
|
|
|
|
|
Original entry may have been skewed by an earlier setting on the device, we
have a confirmed 1000dpi for a new device.
https://github.com/systemd/systemd/issues/1049
|
|
hwdb: add DPI data for a few Logitech mice
|
|
I tested a RX 250 and measured 1000 DPI. The spec for the mouse
agrees:
http://www.logitech.com/en-gb/product/rx250-optical-mouse-business
This is an optical mouse so it is extra sensitive to what kind of
surface it is tested on.
|
|
|
|
|
|
Provided by Francois Marier
|
|
|
|
https://github.com/systemd/systemd/issues/562
|
|
|
|
|
|
DPI information was taken from the device's setup guide.
Additional (shortened) information from udevadm info:
P: .../usb2/2-1/2-1:1.0/0003:046D:C07E.0002/input/input6/event2
N: input/event2
S: input/by-id/usb-Logitech_Gaming_Mouse_G402_6D93117D5049-event-mouse
S: input/by-path/pci-0000:00:12.0-usb-0:1:1.0-event-mouse
...
E: ID_BUS=usb
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_MODEL=Gaming_Mouse_G402
E: ID_MODEL_ENC=Gaming\x20Mouse\x20G402
E: ID_MODEL_ID=c07e
E: ID_PATH=pci-0000:00:12.0-usb-0:1:1.0
E: ID_PATH_TAG=pci-0000_00_12_0-usb-0_1_1_0
E: ID_REVISION=9002
E: ID_SERIAL=Logitech_Gaming_Mouse_G402_6D93117D5049
E: ID_SERIAL_SHORT=6D93117D5049
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:030102:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=Logitech
E: ID_VENDOR_ENC=Logitech
E: ID_VENDOR_ID=046d
E: LIBINPUT_DEVICE_GROUP=3/46d/c07e/111:usb-0000:00:12.0-1
E: MAJOR=13
E: MINOR=66
E: SUBSYSTEM=input
...
|
|
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
|