From: Alex Hung <alex.hung@canonical.com>
To: Alex Hung <alex.hung@canonical.com>
Cc: corentincj@iksaif.net, mjg@redhat.com,
acpi4asus-user@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] eeepc-wmi: change wireless key event to toggle all wireless devices.
Date: Wed, 20 Jun 2012 11:27:47 +0800 [thread overview]
Message-ID: <4FE14333.6020209@canonical.com> (raw)
In-Reply-To: <1340162788-531-1-git-send-email-alex.hung@canonical.com>
Hi All,
This patch needs to work with another fix in net/rfkill/core.c
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next.git;a=commit;h=27e49ca95570c4685a32be9d4664f2b0b6d89368
On 06/20/2012 11:26 AM, Alex Hung wrote:
> The original key event from Fn+F2 hotkey only toggles the state of wireless
> LAN and leaves other wireless devices such as bluetooth uncontrolled. This
> fix change Fn+F2 to generate an event to toggle all wireless devices.
>
> Signed-off-by: Alex Hung<alex.hung@canonical.com>
> ---
> drivers/platform/x86/eeepc-wmi.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/platform/x86/eeepc-wmi.c b/drivers/platform/x86/eeepc-wmi.c
> index 5568c43..ef361fc 100644
> --- a/drivers/platform/x86/eeepc-wmi.c
> +++ b/drivers/platform/x86/eeepc-wmi.c
> @@ -68,7 +68,7 @@ static const struct key_entry eeepc_wmi_keymap[] = {
> { KE_KEY, 0x31, { KEY_VOLUMEDOWN } },
> { KE_KEY, 0x32, { KEY_MUTE } },
> { KE_KEY, 0x5c, { KEY_F15 } }, /* Power Gear key */
> - { KE_KEY, 0x5d, { KEY_WLAN } },
> + { KE_KEY, 0x5d, { KEY_RFKILL } },
> { KE_KEY, 0x6b, { KEY_TOUCHPAD_TOGGLE } }, /* Toggle Touchpad */
> { KE_KEY, 0x82, { KEY_CAMERA } },
> { KE_KEY, 0x83, { KEY_CAMERA_ZOOMIN } },
next prev parent reply other threads:[~2012-06-20 3:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 3:26 [PATCH] eeepc-wmi: change wireless key event to toggle all wireless devices Alex Hung
2012-06-20 3:27 ` Alex Hung [this message]
2012-06-26 18:33 ` Matthew Garrett
2012-06-28 6:59 ` Alex Hung
2012-06-28 13:49 ` Matthew Garrett
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=4FE14333.6020209@canonical.com \
--to=alex.hung@canonical.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentincj@iksaif.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.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;
as well as URLs for NNTP newsgroup(s).