summaryrefslogtreecommitdiff
path: root/kernel/Makefile
diff options
context:
space:
mode:
authorAceLan Kao <acelan.kao@canonical.com>2012-07-04 03:19:08 (GMT)
committerMatthew Garrett <mjg@redhat.com>2012-07-28 04:28:53 (GMT)
commitd2044c5a3aafac552d28c1add16930821c24cbd0 (patch)
tree79c8c162665f644a3152dbd7f0314d6b71e11f43 /kernel/Makefile
parent0ece8d515c264078a144bc597d0ffc40645ce378 (diff)
downloadlinux-d2044c5a3aafac552d28c1add16930821c24cbd0.tar.xz
asus-nb-wmi: add wapf quirk for ASUS machines
The BIOS of these machines will try to enable/disable wifi/bt in their own sqeuence. It won't read the enable/disable parameter in WMI command, but just iterates the wifi/bt's status described below 1st. enable wifi, enable bt 2nd. disable wifi, enable bt 3rd. enable wifi, disable bt 4th. disable wifi, disable bt That will totally mess up the rfkill status, since we will try to read wifi and bt's status and reset it again while booting up. To avoid this, these machines should set the wapf value to 4, that will let software totally control the wifi/bt's status and BIOS will do nothing instead of sending out the 0x88(KEY_RFKILL) event instead of 0x5e(wifi enable), 0x5f(wifi diable), 0x7d(bt enable), and 0x7e(bt disable) through WMI. With this patch[1], it will handle the KEY_RFKILL event correctly and will block/unblock wifi and bt together. 1. https://lkml.org/lkml/2012/5/21/75 Signed-off-by: AceLan Kao <acelan.kao@canonical.com> Signed-off-by: Matthew Garrett <mjg@redhat.com>
Diffstat (limited to 'kernel/Makefile')
0 files changed, 0 insertions, 0 deletions