On Tue, 27 Sep 2011, Johannes Berg wrote:

quoted

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

Because the platform driver is doing the wrong thing.

Hmm?  Is it?

quoted

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.

No, you need to fix the thinkpad driver.

Eh, I can certainly blacklist platform rfkill support for the x201i on the
grounds that it is a piece of crap, since a hardware button that does it in
software is clearly el-cheap-o land that does not belong to something that
dares call itself a ThinkPad X-series.  But I am not sure this is the best
way to go about it.  It will cause that switch to become useless, for one.

I can map it to a soft rfkill button, which seems to be more in line with
the real truth behind it.  But this is very weird, the EC used to even kick
bluetooth out of the USB bus when that switch was enabled...

dmidecode dump, please.  And I'd really appreciate a _full_ report of the
issue and behaviour of the rfkill hw button on the x201i, please send it to
ibm-acpi-devel@lists.sourceforge.net, and we can take the thread there.

I'd ask it to be done through bugzilla.kernel.org, but that's still down.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh