diff options
| author | AceLan Kao <acelan.kao@canonical.com> | 2012-07-27 16:51:59 +0800 |
|---|---|---|
| committer | Matthew Garrett <matthew.garrett@nebula.com> | 2013-02-24 14:49:52 -0800 |
| commit | 6cae06e603339f99334bc6b276e2ac619cf0d476 (patch) | |
| tree | 8c42fb743dd64b92d54973de71b984e49f81d7c0 /lib/swiotlb.c | |
| parent | 9e2d59ad580d590134285f361a0e80f0e98c0207 (diff) | |
asus-wmi: update wlan LED through rfkill led trigger
For those machines with wapf=4, BIOS won't update the wireless LED,
since wapf=4 means user application will take in chage of the wifi and bt.
So, we have to update wlan LED status explicitly.
But I found there is another wireless LED bug in launchpad and which is
not in the wapf=4 quirk.
So, it might be better to set wireless LED status explicitly for all
machines.
BugLink: https://launchpad.net/bugs/901105
Signed-off-by: AceLan Kao <acelan.kao@canonical.com>
Signed-off-by: Matthew Garrett <mjg@redhat.com>
Diffstat (limited to 'lib/swiotlb.c')
0 files changed, 0 insertions, 0 deletions