summaryrefslogtreecommitdiff
path: root/hwdb/60-keyboard.hwdb
AgeCommit message (Collapse)Author
2016-04-25Hp Folio 1040g2 micmute and toggle touchpad fn keys fix (#3118)EMOziko
Added HP Folio 1040g2 Fn+F8 MICMUTE FIx
2016-04-11keymap: Add HP ProBook 640 G2Martin Pitt
Fixes #2997
2016-03-01keymap: Some HP refactoring, add Probook 440 G3 keysMartin Pitt
Apparently the vendor string for newer models now uses "svnHP" instead of "svnHewlett-Packard", so add this alternative match to the global HP map. Generalize matches for micmute key on ProBook 4xx. Silence two hardwired keys on the ProBook 440 G3 that should not produce evdev events. Thanks to Hermann Kraus for those! (See PR #2679)
2016-03-01keymap: Add HP ZBookMartin Pitt
https://launchpad.net/bugs/1535219
2016-01-20Merge pull request #2222 from snakeroot/eventsplatDaniel Mack
hwdb: remove references to udevadm info /dev/input/event*
2016-01-18keymap: Add HP ProBook 440 G3Martin Pitt
Fixes #2343
2016-01-06keymap: remap microphone mute keycode for Lenovo Thinkcentre M800zHui Wang
This Lenovo machine use codec Line2 to implement a microphone mute button, it depends on the unsolicited interrupt to generate key event, the scan code for this button is assigned to 0x00 in the linux kernel driver, and the keycode is KEY_MICMUTE(248), we need to remap this keycode to KEY_F20 to make this hotkey work in X11. BugLink: https://bugs.launchpad.net/bugs/1531362 Signed-off-by: Hui Wang <hui.wang@canonical.com>
2015-12-24hwdb: remove references to udevadm info /dev/input/event*Chris Atkinson
2015-10-18hwdb: fix a syntax error in 60-keyboardMantas Mikulėnas
2015-10-16keymap: Add HP ProBook 6555bMartin Pitt
Thanks to Olaf Hering!
2015-10-14keymap: Drop ThinkPad YogaMartin Pitt
The Yoga's firmware sends key events whenever it's being folded or unfolded. These are thus *not* a button for requesting a screen orientation change, just an indication that this already happened. Thus they should not be assigned to "direction", but be ignored. Assigning them to "reserved" does not silence the "unknown key pressed" kernel warning, so there's no point in maintaining a mapping here. Fixes #1440
2015-10-08keymap: Update Thinkpad Yoga 12 (2015)Martin Pitt
Follow-up commit to e1fd19958: Add d8 scan code as well. Fixes #1440
2015-10-04keymap: Add Thinkpad Yoga 12 (2015)Martin Pitt
Fixes #1440
2015-09-17Revert "keymap: Add Corsair K70"Martin Pitt
This breaks the same vendor/product ID with the German keyboard layout. As this is a hack around some weird keyboard driver bug, let's revert until this is understood better. See https://github.com/systemd/systemd/issues/1243 This reverts commit a2aa71a9542492d6b34007b9dac28e4f10b4256d.
2015-09-14keymap: Add Corsair K70Martin Pitt
2015-09-10Add microphone mute keymap for Dell PrecisionChen-Han Hsiao (Stanley)
2015-08-04Update bugtracker addressZbigniew Jędrzejewski-Szmek
2015-06-14hwdb: add support for Alienware graphics amplifierMario Limonciello
Unplugging and plugging in the cable will create various scancodes on the keyboard controller. Userspace within X should be able to interact with these to show interesting messages. Assign them to generic prog1/prog2. (David: add comment to hwdb explaining that these keycodes are reserved)
2015-06-10keymap: Add Samsung NP350V and NP670Zdslul
typo keymap: Add Samsung NP350V and NP670Z
2015-04-13hwdb: Fix wireless switch on Dell LatitudeMartin Pitt
It does not generate a release event. https://launchpad.net/bugs/1441849
2015-04-11hwdb: add Samsung ATIV Book 6 / 8Gavin Li
This adds support for the keyboard illumination keys and fixes Fn+F1.
2015-04-11udev: builtin-keyboard: add support for EVDEV_ABS_*Peter Hutterer
Parse properties in the form EVDEV_ABS_00="<min>:<max>:<res>:<fuzz>:<flat>" and apply them to the kernel device. Future processes that open that device will see the updated EV_ABS range. This is particularly useful for touchpads that don't provide a resolution in the kernel driver but can be fixed up through hwdb entries (e.g. bcm5974). All values in the property are optional, e.g. a string of "::45" is valid to set the resolution to 45. The order intentionally orders resolution before fuzz and flat despite it being the last element in the absinfo struct. The use-case for setting fuzz/flat is almost non-existent, resolution is probably the most common case we'll need. To avoid multiple hwdb invocations for the same device, replace the hwdb "keyboard:" prefix with "evdev:" and drop the separate 60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes anyway, we don't need a separate rules file and second callout to the hwdb builtin.
2015-03-19hwdb: add HP ProBook 450G0Zbigniew Jędrzejewski-Szmek
https://bugs.freedesktop.org/show_bug.cgi?id=89684
2015-03-16rules: keyboard - prefix "atkbd" match strings like we prefix the "name" stringsKay Sievers
2015-03-16Revert "hwdb: merge atkbd into platform matches"David Herrmann
This reverts commit ba76ee29bc02879fb42c048132af8889b00220d5. As it turns out, we need to match on driver=atkbd to not load the fixups on any plugged USB devices. That is, whenever you use "name:<name>:dmi:<dmi>" style matches, you better provide a name or you're screwing things up.
2015-03-16rules: keyboard - remove "platform" from commentsKay Sievers
2015-03-16hwdb: merge atkbd into platform matchesDavid Herrmann
Currently, we always run hwdb 'keyboard:name:$attr{name}:$attr{[dmi/id]modalias}' as last step to match keyboards. Therefore, if nothing else matched so far, we still try the device-name+dmi combination. However, we have a special atkbd rule which is only run for atkbd as: hwdb 'keyboard:$attr{[dmi/id]modalias}' This is redundant, as we already pass the same information to hwdb in the last fallback step. This patch converts the hwdb "keyboard:dmi:*" matches to "keyboard:name:*:dmi:*" matches and drops the redundant rule.
2015-03-16hwdb: convert to generic input-modalias matchesDavid Herrmann
There is no reason to match on usb-modaliases, if we can use the input-modalias to achieve the same. This commit changes the keyboard-lookups to not be restricted to USB, but pass all modaliases to the hwdb. Furthermore, we convert all usb:* matches to input:* matches, thus getting rid of any ambiguity if multiple usb devices are chained (or a bluetooth device / etc. is on top). Note that legacy keyboard:usb:* matches are still supported, but deprecated. If possible, please use keyboard:input:* matches instead. This is a required step to make other input devices work with 60-keyboard.hwdb. Other bus-types are often chained on usb and we want to avoid any ambiguity here if we incorrectly match on a USB hub.
2015-03-04hwdb: fix Dell XPS12 9Q33 key nameZbigniew Jędrzejewski-Szmek
https://bugs.freedesktop.org/show_bug.cgi?id=84437
2015-02-19hwdb: fix ThinkPad X* Tablet special keysLubomir Rintel
ThinkPad tablet firmware has DMI product name and version reversed: Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: LENOVO Product Name: 7762AS1 Version: ThinkPad X61 Tablet Serial Number: LKZCDH2 UUID: 6ADBC681-4FC9-11CB-844F-B47CB9210BE2 Wake-up Type: Power Switch SKU Number: Not Specified Family: ThinkPad X61 Tablet
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-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
2014-12-17hwdb: add Lenovo 3000 N200 special keyMarc Schmitzer
https://bugs.freedesktop.org/show_bug.cgi?id=87377
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-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>
2014-10-07keymap: Fix touchpad toggle key on Asus laptopsMartin Pitt
https://launchpad.net/bugs/1377352
2014-10-07keymap: Fix touchpad toggle on Toshiba Satellite P75-A7200Martin Pitt
Just like everywhere else we use KEY_F21 instead of KEY_TOUCHPAD_TOGGLE for X friendliness.
2014-09-29udev/hwdb: New Entry for Dell XPS12 9Q33 keyboardStefan Brüns
https://bugs.freedesktop.org/show_bug.cgi?id=84437
2014-08-27keymap: Adjust for more Samsung 900X4 seriesMartin Pitt
Reportedly also applies to NP900X4B, so relax the match to apply to all models of this series. https://launchpad.net/bugs/902332
2014-08-07hwdb: update format description and document reloadingZbigniew Jędrzejewski-Szmek
https://bugs.freedesktop.org/show_bug.cgi?id=82311
2014-08-05keymap: Fix HP Pavillon DV7Martin Pitt
Properly disable scan code 94 instead of producing KEY_0. https://launchpad.net/bugs/1322770
2014-07-30keymap: Annotate all micmute workaroundsMartin Pitt
Add a comment to all assignments to f20 that this actually should be "micmute" in a future when we aren't limited by X.org's key code limiations any more.
2014-07-30keymap: Add microphone mute keymap for Dell LatitudeHui Wang
On the Dell Latitude, the mic mute key event is generated by wmi driver, the keycode assigned to this hotkey from kernel is KEY_MICMUTE (248), this keycode is too big for xorg to handle, in the xorg, the XF86AudioMicMute is assigned to F20. Please refer to 4e648ea0 of xkeyboard-config. BugLink: https://bugs.launchpad.net/bugs/1326684 BugLink: https://bugs.launchpad.net/bugs/1339998 Signed-off-by: Hui Wang <hui.wang@canonical.com> Signed-off-by: Martin Pitt <martin.pitt@ubuntu.com>
2014-06-04hwdb: fix case-sensitive matchKay Sievers
2014-06-01keyboard: add Plantronics .Audio mute buttonZbigniew Jędrzejewski-Szmek
https://bugs.freedesktop.org/show_bug.cgi?id=79495
2014-05-25keymap: Asus EeePC touchpad toggle keyMartin Pitt
Originally is KEY_TOUCHPAD_TOGGLE, but X.org can't handle the big key events, so use the F21 convention. https://bugs.freedesktop.org/show_bug.cgi?id=72807
generated by cgit v1.2.3-54-g00ecf (git 2.45.2) at 2024-11-16 13:52:09 +0000