summaryrefslogtreecommitdiff
path: root/hwdb
AgeCommit message (Collapse)Author
2015-02-10keymap: Add microphone mute keymap for several HP laptopsHui Wang
On these several HP laptops, the microphone mute hotkey is "Fn+F8" and the scancode for this hotkey is 0x81, but this scancode was mapped to fn_esc in the HP generic keymap section. To fix this problem, we add a machine specific keymap section to add the correct keymap rule. BugLink: https://bugs.launchpad.net/bugs/1409721 BugLink: https://bugs.launchpad.net/bugs/1334968 Signed-off-by: Hui Wang <hui.wang@canonical.com>
2015-02-04hwdb: Bind "toolbox" buttons to the Windows keyBastien Nocera
One would expect pressing the button to go to an overview / show applications mode, we thus map it to leftmeta, the Windows key. See https://bugzilla.gnome.org/show_bug.cgi?id=658602#c17
2015-02-02hwdb: Update database of Bluetooth company identifiersMarcel Holtmann
2015-01-29hwdb: add a touchpad hwdbPeter Hutterer
Currently used to tag devices in the new Lenovo *50 series and the X1 Carbon 3rd. These laptops re-introduced the physical trackpoint buttons that were missing from the *40 series but those buttons are now wired up to the touchpad. The touchpad now sends BTN_0, BTN_1 and BTN_2 for the trackpoint. The same button codes were used in older touchpads that had dedicated scroll up/down buttons. Input drivers need to work around this and thus know what they're dealing with. For the previous gen we introduced INPUT_PROP_TOPBUTTONPAD in the kernel, but the resulting mess showed that these per-device quirks should really live in userspace. The list currently includes the X1 Carbon 3rd PNPID, others will be added as get to know which PNPID they have.
2015-01-17hwdb: restore comments about MSI devicesMaxim Mikityanskiy
Some time ago 95-keymap.rules was replaced by 60-keyboard.hwdb. Original comments for MSI laptops (that were in 95-keymap.rules) were removed, but I think they are important for understanding what's going on. https://bugs.freedesktop.org/show_bug.cgi?id=88412
2015-01-16hwbd: add click angle for the Logitech M325Peter Hutterer
This device has 18 stops per rotation == 20 degree angle. Advertised as "Micro-precise scrolling"
2015-01-15hwdb: add MOUSE_WHEEL_CLICK_ANGLE as propertyPeter Hutterer
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.
2015-01-09hwdb: add Kay's Laser Mouse to the dpi databaseLennart Poettering
2015-01-09hwdb: add missing line between the G400 entriesPeter Hutterer
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
2015-01-09hwdb: note that we care about the maximum frequency in MOUSE_DPIPeter Hutterer
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
2015-01-08hwdb: adjust max frequency of Logitech RX 250Zbigniew Jędrzejewski-Szmek
https://bugs.freedesktop.org/show_bug.cgi?id=87435
2015-01-07hwdb: mouse DPI data, Logitech Gaming Mouse G400Jonas Ådahl
2015-01-05hwdb: fix a typoPeter Hutterer
2015-01-05hwdb: revert Logitech Optical USB MousePeter Hutterer
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
2014-12-31hwdb: mouse DPI data, Logitech USB Laser Mouse M-U0011-OChristoph Brill
https://bugs.freedesktop.org/show_bug.cgi?id=87880
2014-12-30hwdb: mouse DPI data, Logitech M-UAS144Christoph Brill
https://bugs.freedesktop.org/show_bug.cgi?id=87881
2014-12-30hwdb: mouse DPI data, Fujitsu Siemens OEMChristoph Brill
https://bugs.freedesktop.org/show_bug.cgi?id=87879
2014-12-30hwdb: mouse DPI data, Logitech MK260 aka M-R0011Christoph Brill
https://bugs.freedesktop.org/show_bug.cgi?id=87882
2014-12-30hwdb: mouse DPI data, Chicony 2.4G Multimedia Wireless KitChristoph Brill
https://bugs.freedesktop.org/show_bug.cgi?id=87883
2014-12-29hwdb: Update database of Bluetooth company identifiersMarcel Holtmann
2014-12-26hwdb: mouse - add Razer AbyssusTom Gundersen
2014-12-24hwdb: add rule and first entry for PS/2 micePeter Hutterer
https://bugs.freedesktop.org/show_bug.cgi?id=87037
2014-12-24hwdb: Microsoft Wireless Laser Mouse 8000 DPI dataFrank Theile
https://bugs.freedesktop.org/show_bug.cgi?id=87587
2014-12-22hwdb: Lenovo USB mouse MO28UOL DPI dataFrank Theile
https://bugs.freedesktop.org/show_bug.cgi?id=87504
2014-12-18hwdb: move Logitech mouse to the right spotZbigniew Jędrzejewski-Szmek
2014-12-18hwdb: Logitech, Inc. RX 250 Optical Mouse DPI dataErik Auerswald
https://bugs.freedesktop.org/show_bug.cgi?id=87435
2014-12-18hwdb: Logitech, Inc. RX 300 Optical Mouse DPI dataTim JP
https://bugs.freedesktop.org/show_bug.cgi?id=87456
2014-12-17hwdb: add Lenovo 3000 N200 special keyMarc Schmitzer
https://bugs.freedesktop.org/show_bug.cgi?id=87377
2014-12-16hwdb: Logitech MX1000, another Lenovo USB mousePeter Hutterer
Provided by Benjamin Bellec https://bugs.freedesktop.org/show_bug.cgi?id=87343
2014-12-16hwdb: more an entry for the MS Sculpt ErgonomicPeter 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-15hwdb: fix orderingDaniel Mack
We sort by default DPI, not the first one in the list.
2014-12-15hwdb: Logitech G400sDaniel Mack
Provided by Peter Hutterer: https://bugs.freedesktop.org/show_bug.cgi?id=87332
2014-12-15hwdb: Logitech MX 518Harald Hoyer
2014-12-12hwdb: add more miceZbigniew Jędrzejewski-Szmek
https://bugs.freedesktop.org/show_bug.cgi?id=87271
2014-12-12hwdb: sort mice by brand,type,dpi,frequencyZbigniew 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-11hwdb: Update database of Bluetooth company identifiersMarcel Holtmann
2014-12-10hwdb: fix typoTorstein Husebø
2014-12-10hwdb: add two more mice to the DPI databaseLennart Poettering
2014-12-10hwdb: add another Logitech mouse (M-BZ96C)Lennart Poettering
2014-12-10hwdb: add DPI data for M325 mouseLennart Poettering
2014-12-10hwdb: update PCI, USB, OUI databasesLennart Poettering
2014-12-10hwdb: add more mouse DPI entriesPeter 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-12-04hwdb: Update database of Bluetooth company identifiersMarcel Holtmann
2014-11-27hwdb: add a new db for the DPI/frequency settings of micePeter 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/)
2014-11-25hwdb: fix a typoPeter Hutterer
2014-11-13keymap: Fix special keys on ThinkPad X60/X61 TabletBastien Nocera
KEY_DIRECTION is mapped to XF86RotateWindows, to rotate the display: http://cgit.freedesktop.org/xkeyboard-config/commit/symbols/inet?id=ec875f6f9b7c4028e11d32b071989c682e6502bd And F13 is mapped to XF86Tools, which is closest to the original toolbox usage: http://cgit.freedesktop.org/xkeyboard-config/tree/symbols/inet?id=7a2c4bed212ebbcc05f3c959aef659ce7dd31fd8#n221
2014-11-13keymap: Add support for IBM ThinkPad X41 TabletBastien Nocera
Scancode taken from: http://www.thinkwiki.org/wiki/Tablet_Hardware_Buttons#Linux_Support William Jon McCann provided the DMI match. IBM seems to have swapped the version and model of the system: Manufacturer: IBM Product Name: 18666TU Version: ThinkPad X41 Tablet
2014-10-31hwdb: Update database of Bluetooth company identifiersMarcel Holtmann
2014-10-30keymap: Ignore brightness keys on Dell Inspiron 1520 to avoid double eventsHans de Goede
On the Dell Inspiron 1520 both the atkbd and acpi-video input devices report an event for pressing the brightness up / down key-combos, resulting in user space seeing double events and increasing / decreasing the brightness 2 steps for each keypress. This hwdb snippet suppresses the atkbd events, making the Inspiron 1520 work like most modern laptops which emit brightness up / down events through acpi-video only. Reported by Pavel Malyshev <p.malishev@gmail.com> https://bugzilla.redhat.com/show_bug.cgi?id=1141525
2014-10-22hwdb: Add mapping for special keys on compaq ku 0133 keyboardsHans de Goede
The compaq ku 0133 keyboard has 8 special keys at the top: http://lackof.org/taggart/hacking/keyboard/cpqwireless.jpg 3 of these use standard HID usage codes from the consumer page, the 5 others use part of the reserved 0x07 - 0x1f range. This commit adds mapping for this keyboard for these reserved codes, making the other 5 keys work. Cc: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
generated by cgit v1.2.3-54-g00ecf (git 2.45.2) at 2024-11-09 23:57:43 +0000