From 0889107a0a7e35d6f6f5946e4c2d2a923a01adfc Mon Sep 17 00:00:00 2001 From: Kai-Heng Feng Date: Wed, 14 Jul 2021 13:20:13 +0800 Subject: [PATCH 1/2] hwdb: Remove intel-hid rfkill mask Turns out HP is phasing out hp-wireless in new models, so we need to use intel-hid for rfkill events. To have best backward and forward compatibility, the solution is implemented in userspace: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda --- hwdb.d/60-keyboard.hwdb | 6 ------ 1 file changed, 6 deletions(-) diff --git a/hwdb.d/60-keyboard.hwdb b/hwdb.d/60-keyboard.hwdb index 2e06143697..2c7711f45d 100644 --- a/hwdb.d/60-keyboard.hwdb +++ b/hwdb.d/60-keyboard.hwdb @@ -494,9 +494,6 @@ evdev:input:b0003v0458p0708* # Hewlett Packard ########################################################### -evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:* - KEYBOARD_KEY_8=unknown # Use hp-wireless instead - evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*:* evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:* KEYBOARD_KEY_81=fn_esc @@ -560,9 +557,6 @@ evdev:atkbd:dmi:bvn*:bvr*:svnHP*:pnHPElitex21013G3:* KEYBOARD_KEY_92=brightnessdown KEYBOARD_KEY_97=brightnessup -evdev:name:Intel HID events:dmi:bvn*:bvr*:svnHP*:pnHPElitex21013G3:* - KEYBOARD_KEY_08=unknown # rfkill is also reported by HP Wireless hotkeys - # Elitebook evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*Compaq*:* evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*EliteBook*:* From 3c88ade5a0d13021537853ce2a2f2f62b8be2a80 Mon Sep 17 00:00:00 2001 From: Kai-Heng Feng Date: Wed, 11 Aug 2021 23:00:11 +0800 Subject: [PATCH 2/2] NEWS: Note Intel HID rfkill mask is removed --- NEWS | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/NEWS b/NEWS index d79f859fa1..6a4b2c0621 100644 --- a/NEWS +++ b/NEWS @@ -518,6 +518,11 @@ CHANGES WITH 249: distribution does not install it yet, it might make sense to change that. + * Intel HID rfkill event is no longer masked, since it's the only + source of rfkill event on newer HP laptops. To have both backward and + forward compatibility, userspace daemon needs to debounce duplicated + events in a short time window. + Contributions from: Aakash Singh, adrian5, Albert Brox, Alexander Sverdlin, Alexander Tsoy, Alexey Rubtsov, alexlzhu, Allen Webb, Alvin Šipraga, Alyssa Ross, Anders Wenhaug,