hwdb: move Logitech M-U0007 [M500] to 1000dpi http://www.logitech.com/en-gb/product/corded-mouse-m500

hwdb: remove references to udevadm info /dev/input/event*

Added support to the wireless mouse Logitech M560.

hwdb: fix typo in G9x DPI Fix typo in DPI: 32000 -> 3200

hwdb: drop weird whitespace Remove whitespace from empty line in hwdb.

G9/G9x change to default resolutions

Add G9 and G9x [Call of Duty MW3 Edition]

Add Mionix Mouse

hwdb: more mice

hwdb: move the Performance MX to 1000dpi 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: update entry for logitech RX 250 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.

hwdb: add a few more mice

hwdb: add DPI data for a few Logitech mice

hwdb: add more DPI entries Provided by Francois Marier

hwdb: add DPI for a few more mice

hwdb: add Logitech G500 (another version) https://github.com/systemd/systemd/issues/562

hwdb: add Logitech LX8 DPI and wheel click settings

Update bugtracker address

hwdb: Add mouse DPI info for Logitech G402. 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 ...

hwdb: Update info for potential contributors. Update the location of the bug tracker and mention that pull requests are preferred.

hwdb: add HP USB 1000dpi Laser Mouse

hwdb: add Logitech MX Master DPI settings

hwdb: move a couple of entries to expected sort order

hwdb: add Logitech MX Revolution

hwdb: update Logitech's unifying receiver devices 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>

hwdb: add Logitech TrackMan Marble Wheel USB DPI is guesswork, no specs found on the web and calculating DPIs on a trackball is tedious.

hwdb: add Apple MagicMouse entry

hwdb: add MS Arc Touch Mouse SE https://bugs.freedesktop.org/show_bug.cgi?id=90540

hwdb: add Logitech M570 trackball http://www.logitech.com/en-us/product/wireless-trackball-m570#specs https://bugzilla.redhat.com/show_bug.cgi?id=1217881

hwdb: fix typo - "sort by by..." -> "sort by..."

hwdb: add HP X1000 DPI info Device name is PixArt, but it's sold as a HP brand. https://bugs.freedesktop.org/show_bug.cgi?id=90142

hwdb: mouse DPI data, Roccat Lua (ROC-11-310) https://bugs.freedesktop.org/show_bug.cgi?id=89743

hwdb: add Logitech G5 Laser Mouse

hwdb: fix syntax

hwdb: Microsoft Microsoft 3-Button Mouse https://bugs.freedesktop.org/show_bug.cgi?id=89149

hwbd: add click angle for the Logitech M325 This device has 18 stops per rotation == 20 degree angle. Advertised as "Micro-precise scrolling"

hwdb: add MOUSE_WHEEL_CLICK_ANGLE as property Most mice have a wheel click angle of 15 degrees, i.e. 24 clicks per full wheel rotation. Some mice, like the Logitech M325 have a larger angle. To allow userspace to make use of that knowledge, add a property to the hwdb. This allows for better predictive scrolling. e.g. a mouse that has a smaller click angle will scroll faster, with this value you can accommodate this where needed. Likewise, using "half turn of the wheel" or "full turn of the wheel" as a UI element becomes possible. This addition is mainly driven by libinput 0.8, having the angle enables libinput to provide an API that distinguishes between a physical distance (like touchpad scrolling does) and discrete steps (wheel clicks). Callers can choose what they prefer based on the device.

hwdb: add Kay's Laser Mouse to the dpi database

hwdb: add missing line between the G400 entries 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

hwdb: note that we care about the maximum frequency in MOUSE_DPI 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

hwdb: adjust max frequency of Logitech RX 250 https://bugs.freedesktop.org/show_bug.cgi?id=87435

hwdb: mouse DPI data, Logitech Gaming Mouse G400

hwdb: fix a typo

hwdb: revert Logitech Optical USB Mouse 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

hwdb: mouse DPI data, Logitech USB Laser Mouse M-U0011-O https://bugs.freedesktop.org/show_bug.cgi?id=87880

hwdb: mouse DPI data, Logitech M-UAS144 https://bugs.freedesktop.org/show_bug.cgi?id=87881

hwdb: mouse DPI data, Fujitsu Siemens OEM https://bugs.freedesktop.org/show_bug.cgi?id=87879

hwdb: mouse DPI data, Logitech MK260 aka M-R0011 https://bugs.freedesktop.org/show_bug.cgi?id=87882

hwdb: mouse DPI data, Chicony 2.4G Multimedia Wireless Kit https://bugs.freedesktop.org/show_bug.cgi?id=87883

hwdb: mouse - add Razer Abyssus

hwdb: add rule and first entry for PS/2 mice https://bugs.freedesktop.org/show_bug.cgi?id=87037

hwdb: Microsoft Wireless Laser Mouse 8000 DPI data https://bugs.freedesktop.org/show_bug.cgi?id=87587

hwdb: Lenovo USB mouse MO28UOL DPI data https://bugs.freedesktop.org/show_bug.cgi?id=87504

hwdb: move Logitech mouse to the right spot

hwdb: Logitech, Inc. RX 250 Optical Mouse DPI data https://bugs.freedesktop.org/show_bug.cgi?id=87435

hwdb: Logitech, Inc. RX 300 Optical Mouse DPI data https://bugs.freedesktop.org/show_bug.cgi?id=87456

hwdb: Logitech MX1000, another Lenovo USB mouse Provided by Benjamin Bellec https://bugs.freedesktop.org/show_bug.cgi?id=87343

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.

hwdb: fix ordering We sort by default DPI, not the first one in the list.

hwdb: Logitech G400s Provided by Peter Hutterer: https://bugs.freedesktop.org/show_bug.cgi?id=87332

hwdb: Logitech MX 518

hwdb: add more mice https://bugs.freedesktop.org/show_bug.cgi?id=87271

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.

hwdb: fix typo

hwdb: add two more mice to the DPI database

hwdb: add another Logitech mouse (M-BZ96C)

hwdb: add DPI data for M325 mouse

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

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/)