From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Keng-Yu Lin <keng-yu.lin@canonical.com>
Cc: len.brown@intel.com, alan-jenkins@tuffmail.co.uk,
superm1@ubuntu.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dell-laptop: Add hwswitch_only module parameter
Date: Thu, 7 Oct 2010 12:15:10 +0100 [thread overview]
Message-ID: <20101007111510.GA19624@srcf.ucam.org> (raw)
In-Reply-To: <1286422207-14248-1-git-send-email-keng-yu.lin@canonical.com>
On Thu, Oct 07, 2010 at 11:30:07AM +0800, Keng-Yu Lin wrote:
> Some BIOS does not report the correct state of the wireless killswitch
> in the return value of SMI Class 17, Select 11.
>
> This causes the killswitch to always stay as soft-blocked once the rfkill
> hotkey is pressed.
>
> This patch adds a module parameter to work around this by disregarding
> the software rfkill and using only Bit 16 in the return value of
> SMI Class 17, Select 11 as the hardware killswitch.
I don't like "Fix my hardware" options. Is there any way we can identify
this failure case?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-10-07 11:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 3:30 [PATCH] dell-laptop: Add hwswitch_only module parameter Keng-Yu Lin
2010-10-07 11:15 ` Matthew Garrett [this message]
[not found] ` <AANLkTinus8SxbXt14qabXgpbFXF4U+uNoKA-=eDuOjmp@mail.gmail.com>
2010-10-07 13:35 ` Matthew Garrett
2010-10-07 20:49 ` Mario Limonciello
2010-10-07 20:50 ` Matthew Garrett
2010-10-07 20:53 ` Mario Limonciello
2010-10-07 21:24 ` Matthew Garrett
2010-10-07 21:30 ` Dmitry Torokhov
2010-10-07 21:33 ` Mario Limonciello
2010-10-07 21:37 ` Matthew Garrett
2010-10-07 21:41 ` Mario Limonciello
2010-10-07 21:42 ` Matthew Garrett
2010-10-07 21:45 ` Mario Limonciello
2010-10-07 21:49 ` Matthew Garrett
2010-10-07 21:52 ` Mario Limonciello
2010-10-07 21:46 ` Dmitry Torokhov
2010-10-07 21:49 ` Mario Limonciello
2010-10-07 21:50 ` Matthew Garrett
2010-10-07 21:57 ` Mario Limonciello
2010-10-07 21:58 ` Dmitry Torokhov
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=20101007111510.GA19624@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=keng-yu.lin@canonical.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=superm1@ubuntu.com \
/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.