summaryrefslogtreecommitdiff
path: root/hwdb/60-keyboard.hwdb
AgeCommit message (Collapse)Author
2017-04-20hwdb: fix warning "atkbd serio0: Unknown key pressed" (#5772)Franck Bui
At each time pressing the WiFi Fn key on Dell Latitude E7270 laptop, the system reports the following error/warning messages: atkbd serio0: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0). atkbd serio0: Use 'setkeycodes e008 ' to make it known. This is due to commit 0e33634 which was added to fix https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1441849. However on Dell Latitude E7* models, we need to restore the old generic behavior which consists in ignoring the key event since it's already done by the HW. Indeed the hardware has a specific driver (dell_wmi) to handle rfkill in the hardware level. So, as long as the hardware handles, the best is to leave as is. This patch was originally written by Takashi Iwai. Fixes #5047
2017-04-12hwdb: Add power button mapping for Acer modelsChris Chiu
The power key keycode e076 is emitted on several different Acer laptop models, and it is expected that it will also be used on upcoming models. Verified on the following models: Aspire ES1-421 Aspire ES1-432 Aspire A515-51 Aspire A515-51G Aspire A517-51 Aspire A517-51G Nitro AN515-31
2017-04-12hwdb: Fix airplane mode key for all Acer seriesChris Chiu
According to the key code v2.02 from Acer, scancode E0 86 will be generated for airplane mode hotkey. Verified on Aspire, TravelMate, Easynote and Predator.
2017-04-12hwdb: Map 0x8a to F20 on the Acer Travelmate P648-G2-MGJoão Paulo Rechi Vita
This model emits 0x9a for the microphone mute button above the keyboard, so let's map it to correct keycode.
2017-03-09hwdb: Add new quirk type to documentationBastien Nocera
Missed in b698b5c.
2017-03-09hwdb: Add property for keyboards without LEDsBastien Nocera
It is useful for desktop environments to be able to show Caps-Lock or Num-Lock status changes as an on-screen display when using a keyboard that doesn't have LEDs for this. Closes: #5559
2017-03-09hwdb: Better documentation for keyboard quirksBastien Nocera
Split up the device matching explanation, and add documentation for the fixed layout quirk.
2017-02-27hwdb: release PageUp on Acer Aspire 7750G (#5476)xTibor
2017-02-12hwdb: Cube iwork8 air button keymap fixupHans de Goede
The home and power buttons on the Cube iwork8 air tablet are swapped, add a hwdb entry fixing this up. Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2017-02-12rules: Add extended evdev/input match rules for event nodes with the same nameHans de Goede
Sometimes a system may have 2 input event nodes with the same name where we only want to apply keyboard hwdb rules to 1 of the 2 devices. This problem happens e.g. on devices where the soc_button_array driver is used (e.g. intel atom based tablets) which registers 2 event nodes with the name "gpio-keys". This commit adds a new extended match rule which extends the match to also check $attr{phys} and $attr{capabilities/ev}, allowing to differentiate between devices with an identical name. Suggested-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2017-01-11hwdb: update micmute YCODE on device node at DELL LATITUDE laptops for mic ↵nikolaof
mute button. (#5012)
2016-12-22hwdb: clarify where to find the modalias and vid/pid information (#4952)Peter Hutterer
Fixes #4938
2016-12-06hwdb: Add fixed layout for another YubikeyBastien Nocera
2016-12-06hwdb: Add fixed layout for OKE barcode readerBastien Nocera
2016-12-01hwdb: add XKB_FIXED_LAYOUT/VARIANT to the keyboard hwdbPeter Hutterer
Yubikeys and other pseudo keyboards require that they are in the US layout, otherwise the data they send is invalid. Add two new keys to signal this to processes that handles (XKB) layouts.
2016-12-01hwdb: fix comment referring to rules filePeter Hutterer
60-keyboard.rules was renamed to 60-evdev.rules in 51c0c2869 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2016-11-24hwdb: fix syntax error in 60-keyboard.hwdbMartin Pitt
Fixes #4728
2016-11-23hwdb: use systemd-hwdb instead of obsolete udevadm hwdb (#4722)Michael Biebl
Fixes: #4721
2016-11-19hwdb: keyboard: Ignore brightness hotkey presses on MSI VR420 (model ↵Hans de Goede
MS-1422) (#4696) Add MSI VR420 (model MS-1422) to the list of MSI models which need to ignore brightness hotkey presses, as these are already reported through the acpi-video interface. Bug-link: https://bugzilla.redhat.com/show_bug.cgi?id=1270124 Reported-by: David Dreggors <dadreggors@gmail.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
2016-11-16hwdb: fix airplane mode trigger when switching from laptop to desktop on HP ↵Francesco Brozzu
Pavilion x360 13 (#4680)
2016-10-12hwdb: Treat Latitude 2110 brightness keys like on Inspiron 1520 (#4355)Ben Harris
Like the Inspiron 1520, the Dell Latitude 2110 emits brightness-control key events both through atkbd and acpi-video. This suppresses them on the atkbd side.
2016-08-27hwdb: 60-keyboard: remove line causing a syntax errorMantas Mikulėnas
2016-08-13hwdb: normalize spacing in 60-keyboard.hwdb (#3954)Zbigniew Jędrzejewski-Szmek
2016-08-09hwdb: comment out a duplicated key for the XOZbigniew Jędrzejewski-Szmek
It's hard to say which one of the two mappings should stay. But the later one would win (when both very present), and nobody complained, so let's assume that that's the one.
2016-08-09hwdb: use lowercase hex for key numbersZbigniew Jędrzejewski-Szmek
It seems awkward to have both cases mixes. Note that the real parser accepts both cases, and this only standarizes the usage in the systemd database.
2016-08-09hwdb: indent commented propertiesZbigniew Jędrzejewski-Szmek
This way it's clear that the property block does not end at the comment. The python checker will complain if this is not the case. We had a few bugs before where two match blocks were merged by mistake, and this change should help avoid that.
2016-08-07hwdb: add multimedia keys for Medion Akoya series (#3918)romanstingler
2016-04-29hwdb: add missing newline so the hwdb buils correctly againLennart Poettering
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.