Here's the awnser of the thinkpad_acpi module maintainer: https://www
.mail-archive.com/platform-driver-x86@vger.kernel.org/msg05285.html
To summarize: The patch itself is technically correct and leads to the
old behaviour. But he'd prefer not to apply the patch, because the event
is already propagated through the thinkpad_acpi input device.
The input device is located at /dev/input/by-path/platform-
thinkpad_acpi-event and toggling the switch twice raises the following
events:
$ sudo input-events 6
/dev/input/event6
bustype : BUS_HOST
vendor : 0x17aa
product : 0x5054
version : 16641
name : "ThinkPad Extra Buttons"
phys : "thinkpad_acpi/input0"
bits ev : EV_SYN EV_KEY EV_MSC EV_SW
waiting for events
19:07:04.424098: EV_SW SW_RADIO 0
19:07:04.424098: EV_SYN code=0 value=0
19:07:05.982584: EV_SW SW_RADIO 1
19:07:05.982584: EV_SYN code=0 value=0
I haven't figured out yet, how I can make use of the input event device.
There doesn't seem to be any scriptable daemon listening to it.
Alternativley one can use rfkill uevents via the udev daemon. A working
rule could be:
SUBSYSTEM=="rfkill", ATTR{type}=="wlan", ENV{RFKILL_STATE}=="1",
RUN+="/usr/local/bin/toggle-blue"
I guess this bug can be marked as invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310248
Title:
[Lenovo Thinkpad X220] wireless switch doesn't generate an acpi event
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310248/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
