From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Joey Lee <jlee@novell.com>
Cc: mzxreary@0pointer.de, gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 58/62] msi-laptop: Support some MSI 3G netbook that is need load SCM
Date: Wed, 3 Mar 2010 13:45:33 +0000 [thread overview]
Message-ID: <20100303134533.GA28349@srcf.ucam.org> (raw)
In-Reply-To: <4B8E85AC020000230001413A@novprvlin0050.provo.novell.com>
On Tue, Mar 02, 2010 at 09:52:12PM -0700, Joey Lee wrote:
> I developed this driver on 2.6.31 kernel, and I found this key code is
> in 2.6.33 kernel and later.
> There have one and only one scancode to control 3 devices when end user
> press fn+f11 key on MSI N034.
> Currently, we setup this mapping in HAL key and mapping it to KEY_WLAN.
Ah! The key comes through the keyboard controller? In that case, yeah,
just map it to KEY_RFKILL in hal isntead of KEY_WLAN. Everything should
work fine then. If rfkill-input is configured, it'll kill all the
radios. If userland claims it instead, it can cycle through with
whatever policy is desired.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-03-03 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 4:52 [PATCH 58/62] msi-laptop: Support some MSI 3G netbook that is need load SCM Joey Lee
2010-03-03 13:45 ` Matthew Garrett [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-09 12:42 Joey Lee
2010-03-09 21:01 ` Greg KH
2010-03-09 21:14 ` Matthew Garrett
2010-03-05 6:10 Joey Lee
2010-03-04 17:07 Joey Lee
2010-03-04 17:09 ` Matthew Garrett
2010-03-02 23:09 [GIT PATCH] driver core patches for 2.6.33-git Greg KH
2010-03-02 23:28 ` [PATCH 58/62] msi-laptop: Support some MSI 3G netbook that is need load SCM Greg Kroah-Hartman
2010-03-02 23:39 ` Matthew Garrett
2010-03-02 23:46 ` Greg KH
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=20100303134533.GA28349@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=gregkh@suse.de \
--cc=jlee@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mzxreary@0pointer.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.