keymap: Add HP ProBook 440 G3 Fixes #2343

keymap: remap microphone mute keycode for Lenovo Thinkcentre M800z 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>

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

hwdb: fix a syntax error in 60-keyboard

keymap: Add HP ProBook 6555b Thanks to Olaf Hering!

keymap: Drop ThinkPad Yoga 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

keymap: Update Thinkpad Yoga 12 (2015) Follow-up commit to e1fd19958: Add d8 scan code as well. Fixes #1440

keymap: Add Thinkpad Yoga 12 (2015) Fixes #1440

Revert "keymap: Add Corsair K70" 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.

keymap: Add Corsair K70

Add microphone mute keymap for Dell Precision

Update bugtracker address

hwdb: add support for Alienware graphics amplifier 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)

keymap: Add Samsung NP350V and NP670Z typo keymap: Add Samsung NP350V and NP670Z

hwdb: Fix wireless switch on Dell Latitude It does not generate a release event. https://launchpad.net/bugs/1441849

hwdb: add Samsung ATIV Book 6 / 8 This adds support for the keyboard illumination keys and fixes Fn+F1.

udev: builtin-keyboard: add support for EVDEV_ABS_* 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.

hwdb: add HP ProBook 450G0 https://bugs.freedesktop.org/show_bug.cgi?id=89684

rules: keyboard - prefix "atkbd" match strings like we prefix the "name" strings

Revert "hwdb: merge atkbd into platform matches" 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.

rules: keyboard - remove "platform" from comments

hwdb: merge atkbd into platform matches 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.

hwdb: convert to generic input-modalias matches 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.

hwdb: fix Dell XPS12 9Q33 key name https://bugs.freedesktop.org/show_bug.cgi?id=84437

hwdb: fix ThinkPad X* Tablet special keys 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

keymap: Add microphone mute keymap for several HP laptops 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>

hwdb: Bind "toolbox" buttons to the Windows key 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

hwdb: restore comments about MSI devices 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

hwdb: add Lenovo 3000 N200 special key https://bugs.freedesktop.org/show_bug.cgi?id=87377

hwdb: fix a typo

keymap: Fix special keys on ThinkPad X60/X61 Tablet 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

keymap: Add support for IBM ThinkPad X41 Tablet 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

keymap: Ignore brightness keys on Dell Inspiron 1520 to avoid double events 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

hwdb: Add mapping for special keys on compaq ku 0133 keyboards 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>

keymap: Fix touchpad toggle key on Asus laptops https://launchpad.net/bugs/1377352

keymap: Fix touchpad toggle on Toshiba Satellite P75-A7200 Just like everywhere else we use KEY_F21 instead of KEY_TOUCHPAD_TOGGLE for X friendliness.

udev/hwdb: New Entry for Dell XPS12 9Q33 keyboard https://bugs.freedesktop.org/show_bug.cgi?id=84437

keymap: Adjust for more Samsung 900X4 series Reportedly also applies to NP900X4B, so relax the match to apply to all models of this series. https://launchpad.net/bugs/902332

hwdb: update format description and document reloading https://bugs.freedesktop.org/show_bug.cgi?id=82311

keymap: Fix HP Pavillon DV7 Properly disable scan code 94 instead of producing KEY_0. https://launchpad.net/bugs/1322770

keymap: Annotate all micmute workarounds 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.

keymap: Add microphone mute keymap for Dell Latitude 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>

hwdb: fix case-sensitive match

keyboard: add Plantronics .Audio mute button https://bugs.freedesktop.org/show_bug.cgi?id=79495

keymap: Asus EeePC touchpad toggle key 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

keymap: Add Lenovo Enhanced USB Keyboard https://bugs.freedesktop.org/show_bug.cgi?id=77234

Add hwdb entry for Samsung Series 7 Ultra

hwdb: keymaps for Samsung 900X3E/900X3F Keymaps for Samsung 900X3E and 900X3F should be the same as for other models in the series. I have also moved the comment for '# Series 9' to the right place

replace tabs with spaces in some files Files: * hwdb/60-keyboard.hwdb * shell-completion/zsh/_systemd-coredumpctl * src/test/test-helper.h

keymap: Add Toshiba EQUIUM Thanks Aleksander Kowalski <aleksander.kowalski.1@gmail.com>!

keymap: Add Sony Vaio VGN-FW250 https://launchpad.net/bugs/1271163

keymap: Add release quirk for Acer AOA switchvideomode key https://launchpad.net/bugs/1272658

keymap: Add HP Chromebook 14 (Falco) Thanks to Stefan Nagy <public@stefan-nagy.at>.

hwdb: Add support for Toshiba Satellite P75-A7200 keyboard

keymap: Recognize different Toshiba Satellite capitalizations https://launchpad.net/bugs/665918

hwdb: fix match for Thinkpad X201 tablet https://bugs.freedesktop.org/show_bug.cgi?id=71929

hwdb: remove duplicate entry for Samsung 700Z keyboardbrightnessup/down are not even real keys. https://bugs.freedesktop.org/show_bug.cgi?id=72311

hwdb: add Samsung 700G https://bugs.freedesktop.org/show_bug.cgi?id=72311

hwdb: change key mappings for Samsung 90X3A The Key codes didn't match with the described key. Also the key identifier strings were missing. I hope I chose appropriate ones. https://bugs.freedesktop.org/show_bug.cgi?id=70296

keymap: Refactor Acer tables Move common keys into generic Acer table, and factorize the model specific exceptions.

keymap: Add Toshiba Satellite U940 Signed-off-by: Martin Pitt <martinpitt@gnome.org>

keymap: Fix stuck keys on Lenovo IdeaPad Z370 https://launchpad.net/bugs/1245189

keymap: Reorder IdeaPad rules So that they are together in the file.

keymap: Fix Samsung 900X[34]C It appears that it's not really the 900 vs. 940 or the X3 vs X4, but the A/B/C/D suffix after that which makes the difference between the keymaps. On a NP900X3C-A04RU you get MODALIAS=dmi:bvn*:bvr*:bd*:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:* So change the matches to use AB vs. CDG as the differentiator. Thanks to Anatoly Markov for reporting and testing!

keymap: Add Samsung Ativ 9 Plus https://launchpad.net/bugs/1229936

keymap: Fix wrong assignments to F23 These days, F21/F22/F23 mean Touchpad toggle/on/off. Clean up other assignments to that from ancient times which belong to keys like "Auto Brightness" (which doesn't have a keycode and is usually hardwired) or some "launch vendor tool" key. https://bugs.freedesktop.org/show_bug.cgi?id=62953

keymap: Add Samsung Series 5 [Ultra] Also consolidate the wlan key into the "all Samsung" rule to avoid repetition. Thanks to Mauro Carvalho Chehab! https://bugzilla.redhat.com/show_bug.cgi?id=989103

keymap: remove some commented out lines

hwdb: add Toshiba Satellite P75-A Contributed by Guillermo Dominguez Duarte <guillermod84@gmail.com>.

keymap: Add Asus WMI module We need to override the TOUCHPAD_TOGGLE to F21 to make it useful under X, as for other models.

keymap: Explicitly match "any product name" for "all models from vendor" rules Without this, the hwdb trie gets mis-sorted to match the more specific rules first, as ":pvr" is lexicographically after ":pn". So ensure that all our matches have some ":pn" match to avoid this trap.

keymap: Fix typo in Latitude/Precision rules We actually want to match the product name, "pn:" makes no sense.

keymap: Don't use spaces in DMI modalias matches Spaces get dropped from DMI modaliases. Replace them with '*' to make them robust against future changes in space escaping.

keymap: Fix Dell vendor names Spaces are dropped from vendor and product names in DMI modaliases, so a match like "svnDell Inc.:" will never happen. Also, some machines use "Dell", some "Dell Inc", some "Dell Inc.", so just match on "Dell*" to avoid all these traps. https://launchpad.net/bugs/1218433

keymap: Don't erase previous assignments Don't use "KEYBOARD_KEY_xx=!" assignments (i. e. only enabling force-release) if more general matches already explicitly set a key code before, to not override the previously set value. https://launchpad.net/bugs/1218433

keymap: Add Logitech Internet Navigator variant [PID C309] By Albrecht Kolthoff <kolthoff@gmx.net> via linux-hotplug@.

keymap: Add Samsung NP53U3C https://launchpad.net/bugs/1203853

Keyboard map for Samsung NP700Z3C I'm using Ubuntu 13.04 on a Samsung Series 5 computer and found that that Fn hotkeys does not work.

keyboard: add eMachines E725 Information supplied by Ludvig <enthymeme@lavabit.com>.

keymap: add Pavilion dv7 keys

hwdb: keyboard - remove stray " <dvdhrm> kay, hwdb/60-keyboard.hwdb line 147 it says KEYBOARD_KEY_ee=screenlock" with a " at the end. I guess that's a typo?

hwdb: map logitech R400 presenter keys from powerpoint hotkeys to sensible KEY_ definitions

hwdb: add GIGABYTE U2442 mute key to the force-release list https://bugs.freedesktop.org/show_bug.cgi?id=67651

keymap: add HP EliteBook 2570p's wlan switch to hwdb https://bugs.freedesktop.org/show_bug.cgi?id=66178

hwdb: data update

60-keyboard.hwdb: Fix syntax error Add missing '='.

keymap: re-add Logitech USB corded/cordless models These add back are the remaining 3 udev keymap rules which used name based instead of ID based matching.

switch from udev keymaps to hwdb

hwdb: follow: "keymap: Drop non-existant Samsung 900XC3"

hwdb: keyboard update

hwdb: keyboard -- update comments

hwdb: keyboard -- add file Do not enable/install it now, until we switch over from the current keymap tool.