From: Johannes Stezenbach <js@sig21.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Lukas Hejtmanek <xhejtman@ics.muni.cz>,
reinette chatre <reinette.chatre@intel.com>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: iwlwifi (4965) regression since 2.6.30
Date: Fri, 7 Aug 2009 22:32:26 +0200 [thread overview]
Message-ID: <20090807203226.GA13867@sig21.net> (raw)
In-Reply-To: <20090806230704.GA14381@khazad-dum.debian.net>
On Thu, Aug 06, 2009 at 08:07:04PM -0300, Henrique de Moraes Holschuh wrote:
> On Fri, 07 Aug 2009, Lukas Hejtmanek wrote:
> > 0x0004 = 238 # KEY_WLAN
>
> This means any rfkill input handler (be it in kernel or userspace) will
> toggle your WLAN cards when fn+f5 is pressed. You can just assign a
> different keycode to it (use KEY_RESERVED or KEY_UNKNOWN if you don't want
> the key to do anything).
>
> If you unmask the key on hotkey_mask, it will revert to BIOS actions, which
> depending on the thinkpad, might cause it to operate on bluetooth, wwan,
> etc...
I have a related question, sorry if I hijack the thread...
When thinkpad-acpi grew rfkill support a few kernel versions back
it forced Bluetooth on at boot time. Since I almost never use
Bluetooth I want it off to save power. The workaround I came up
with was to enable CONFIG_RFKILL and add rfkill.default_state=0
to the kernel cmdline. Now this workaround also disables WLAN :-(
My workaround for my workaround (heh!) was to add
pre-up echo 1 > `ls /sys/class/ieee80211/phy0/rfkill*/state`
in /etc/network/interfaces. It would be nice to have a better
way to select boot-up defaults.
In Documentation/laptops/thinkpad-acpi.txt there is this comment
for FN+F5:
Should be used to turn on/off all radios (Bluetooth+W-WAN+WLAN), really.
I disagree. Why would anyone turn off all radios at once?
What I want is to disable the radios I don't need to save power,
so IMHO there should be different keys for Bluetooth and WLAN
(and W-WAN where present).
The BIOS does the right thing for me, it disables Bluetoth by default
until enabled with Fn-F5, and WLAN is always enabled. For me
the rfkill support is a regression, not progress.
Johannes
next prev parent reply other threads:[~2009-08-07 20:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 7:57 iwlwifi (4965) regression since 2.6.30 Lukas Hejtmanek
2009-07-27 16:03 ` reinette chatre
2009-07-27 16:06 ` Johannes Berg
2009-07-28 11:21 ` Lukas Hejtmanek
2009-07-28 12:54 ` Johannes Berg
2009-08-02 22:12 ` Lukas Hejtmanek
2009-08-03 21:47 ` reinette chatre
2009-08-04 8:49 ` Lukas Hejtmanek
2009-08-04 22:49 ` reinette chatre
2009-08-04 22:56 ` Lukas Hejtmanek
2009-08-04 23:38 ` reinette chatre
2009-08-06 13:22 ` Henrique de Moraes Holschuh
2009-08-06 22:41 ` Lukas Hejtmanek
2009-08-06 23:07 ` Henrique de Moraes Holschuh
2009-08-07 20:32 ` Johannes Stezenbach [this message]
2009-08-07 21:16 ` Lukas Hejtmanek
2009-08-07 21:35 ` Lukas Hejtmanek
2009-08-13 22:59 ` reinette chatre
2009-08-14 2:10 ` Henrique de Moraes Holschuh
2009-08-14 16:07 ` reinette chatre
2009-07-27 16:07 ` Marcel Holtmann
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=20090807203226.GA13867@sig21.net \
--to=js@sig21.net \
--cc=hmh@hmh.eng.br \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=xhejtman@ics.muni.cz \
/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