acpi4asus

h1. Asus-laptop WAPF

h2. Bits

In the table below:

* *Hardware control* means pressing the Fn+F2 key will effectively toggle the device state in hardware.

* *Software control* means an ACPI event is generated instead, and must be handled by a device driver or relayed to an application.

|_.WAPF|_.WLAN control|_.BT control|_.?|

|0x0|Hardware|Hardware|No application|

|0x1|Software|Hardware|?|

|0x4|Software|Software|Wireless console|

Note that not all laptop models support all WAPF values; in particular, some laptops are only made for WAPF 0x4 and won't do anything in hardware.

h2. Event Notifications

Pressing the Fn+F2 generates different ACPI notifications depending on the kind of device control mode (see the table above):

* in *hardware*, notifications *inform* the device driver of a state change that has already occurred.

* in *software*, notifications *ask* the device driver to change the device state, but nothing is done in hardware.

|_.WAPF|_.WLAN ON|_.WLAN OFF|_.BT ON|_.BT OFF|

|0x0|0x5E|0x5F|0x7D|0x7E|

|0x1|0x5D|0x5D|0x7D|0x7D|

|0x4|0x88|0x88|0x88|0x88|

h2. In the real world

|_.WAPF|_.M51|_.F3JC|_.A6JC|

|0x0|wb bb|wl bb|wn bd|

|0x1|wl bl|wl bb|wn bd|

|0x2|wb bb|wl bb|wn bd|

|0x3|wl bl|wl bb|wn bd|

|0x4|wl bl|wl bb|wn bd|

|0x5|wl bl|wl bb|wn bd|

bn: BLED control nothing

bl: BLED control the led

bd: BLED control the device

bb: BLED control both

wn: WLED control nothing

wl: WLED control the led

wd: WLED control the device

wb: WLED control both

BLED in controled by /sys/devices/platform/asus-laptop/bluetooth

WLED in controled by /sys/devices/platform/asus-laptop/wlan

You can change the wapf value like that: modprobe -r asus-laptop; modprobe asus-laptop wapf=1 (or 2, 3, 4, 5 ..)