~lukeshu/systemd - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2014-12-22	hwdb: Lenovo USB mouse MO28UOL DPI data	Frank Theile
	https://bugs.freedesktop.org/show_bug.cgi?id=87504
2014-12-18	hwdb: move Logitech mouse to the right spot	Zbigniew Jędrzejewski-Szmek

2014-12-18	hwdb: Logitech, Inc. RX 250 Optical Mouse DPI data	Erik Auerswald
	https://bugs.freedesktop.org/show_bug.cgi?id=87435
2014-12-18	hwdb: Logitech, Inc. RX 300 Optical Mouse DPI data	Tim JP
	https://bugs.freedesktop.org/show_bug.cgi?id=87456
2014-12-16	hwdb: Logitech MX1000, another Lenovo USB mouse	Peter Hutterer
	Provided by Benjamin Bellec https://bugs.freedesktop.org/show_bug.cgi?id=87343
2014-12-16	hwdb: more an entry for the MS Sculpt Ergonomic	Peter 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-15	hwdb: fix ordering	Daniel Mack
	We sort by default DPI, not the first one in the list.
2014-12-15	hwdb: Logitech G400s	Daniel Mack
	Provided by Peter Hutterer: https://bugs.freedesktop.org/show_bug.cgi?id=87332
2014-12-15	hwdb: Logitech MX 518	Harald Hoyer

2014-12-12	hwdb: add more mice	Zbigniew Jędrzejewski-Szmek
	https://bugs.freedesktop.org/show_bug.cgi?id=87271
2014-12-12	hwdb: sort mice by brand,type,dpi,frequency	Zbigniew 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-10	hwdb: fix typo	Torstein Husebø

2014-12-10	hwdb: add two more mice to the DPI database	Lennart Poettering

2014-12-10	hwdb: add another Logitech mouse (M-BZ96C)	Lennart Poettering

2014-12-10	hwdb: add DPI data for M325 mouse	Lennart Poettering

2014-12-10	hwdb: add more mouse DPI entries	Peter 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-27	hwdb: add a new db for the DPI/frequency settings of mice	Peter 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/)