On Tue, Sep 27, 2011 at 3:08 PM, Johannes Berg
[off-list ref] wrote:

On Tue, 2011-09-27 at 13:34 +0400, Andrew V. Stepanov wrote:

quoted

On Tue, Sep 27, 2011 at 12:54 PM, Johannes Berg
[off-list ref] wrote:

quoted

On Tue, 2011-09-27 at 12:46 +0400, Andrew V. Stepanov wrote:

quoted

I wan't to completely ignore events (state) of software\hardware rfkill buttons.

Why would you ever want to do that? I can see that you might want to
ignore soft buttons, but you can use urfkilld for that. Ignoring hard
buttons is completely useless -- they will affect the device they're
wired up to *anyway*.

No. That is not true.

Hardware rfkill button doesn't have any action to wlan\bluetooth
devices on ThinkPad x201i with "CONFIG_RFKILL is not set".
I can assume this is true for other notebooks.

Then why is it a hard button instead of the soft button on a separate
platform device?

johannes

1.

Lenovo ThinkPad x201i has two rfkill buttons.
One soft: Fn-F5.
Second hard: small switch on left case side.

With RFKILL_CONFIG == "is not set" this two buttons became inactive.
They do not has any influence to adapter\drivers state.

This patch give ability disable rfkill sub-system by means to pass
special module parameter.

Example from real life. Some company want to make inactive rfkill
SW+HW buttons on some company notebooks.
For this, you advise to recompile kernel.

2.

One more thing, why this patch is necessary. You advise to use
urfkilld. But this is doesn't help in case of external USB WIFI
devices.

Turn on(off) HW button will be effect on all WIFI devices, even
external. rfkill kernel subsystem will bring all cfg80211 devices to
software lock. See: net/wireless/core.c for rfkill. I do not think,
that urfkilld will help.