From: Jelle van der Waa <jelle@vdwaa.nl>
To: matthew.garrett@nebula.com
Cc: platform-driver-x86@vger.kernel.org
Subject: hp-wmi hp 8570W hardware wifi key
Date: Tue, 02 Apr 2013 15:51:58 +0200 [thread overview]
Message-ID: <515AE27E.8050204@vdwaa.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
Hi,
I recently updated my laptop's BIOS and now my hardware wifi key fails,
it doesn't disable the wifi chip anymore.
In dmesg I found an error message, which indicates a event_id changed. (
dmesg.txt )
I tried to fix the issue by patching hp_wmi.c, to match the new event_id
which seems to be 8, but I couldn't get it working. (
hp_wmi_wireless_event_id_changed.patch ).
I'm willing to test patches and I will try to test if the issues occurs
with the recent rc release of linux.
[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 407 bytes --]
[89172.325510] hp_wmi: Unknown event_id - 8 - 0x2
[89174.314755] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
[89174.314763] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
[89174.495251] atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0).
[89174.495259] atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
[-- Attachment #3: hp_wmi_wireless_event_id_changed.patch --]
[-- Type: text/x-patch, Size: 662 bytes --]
diff -aur linux-3.9-rc6/drivers/platform/x86/hp-wmi.c linux-3.9-rc5/drivers/platform/x86/hp-wmi.c
--- linux-3.9-rc6/drivers/platform/x86/hp-wmi.c 2013-04-02 14:50:59.674132120 +0200
+++ linux-3.9-rc5/drivers/platform/x86/hp-wmi.c 2013-04-02 14:55:51.484149029 +0200
@@ -71,6 +71,7 @@
HPWMI_WIRELESS = 5,
HPWMI_CPU_BATTERY_THROTTLE = 6,
HPWMI_LOCK_SWITCH = 7,
+ HPWMI_WIRELESS_NEW = 8,
};
struct bios_args {
@@ -509,7 +510,7 @@
key_code, 1, true))
pr_info("Unknown key code - 0x%x\n", key_code);
break;
- case HPWMI_WIRELESS:
+ case HPWMI_WIRELESS: case HPWMI_WIRELESS_NEW:
if (rfkill2_count) {
hp_wmi_rfkill2_refresh();
break;
reply other threads:[~2013-04-02 13:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=515AE27E.8050204@vdwaa.nl \
--to=jelle@vdwaa.nl \
--cc=matthew.garrett@nebula.com \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox