FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu Kernel Team

LinkBack Thread Tools
Old 08-28-2012, 06:15 AM
AceLan Kao
Default asus-wmi: update wlan LED through rfkill led trigger

For this issue

We need 2 patches from linux-next tree

commit 06d7de831dab8b93adb86e039a2f3d36604a9197
Author: AceLan Kao <acelan.kao@canonical.com>
Date: Thu Jul 26 09:51:08 2012 +0800

Revert "rfkill: remove dead code"

This reverts commit 2e48928d8a0f38c1b5c81eb3f1294de8a6382c68.

Those functions are needed and should not be removed, or
there is no way to set the rfkill led trigger name.

Signed-off-by: AceLan Kao <acelan.kao@canonical.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit 154a7a7b22342ab9ccde34f583e4b730965ee515
Author: AceLan Kao <acelan.kao@canonical.com>
Date: Fri Jul 27 16:51:59 2012 +0800

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

BugLink: https://launchpad.net/bugs/901105

Signed-off-by: AceLan Kao <acelan.kao@canonical.com>
Signed-off-by: Matthew Garrett <mjg@redhat.com>


Chia-Lin Kao(AceLan)
E-Mail: acelan.kaoATcanonical.com (s/AT/@/)

kernel-team mailing list

Thread Tools

All times are GMT. The time now is 05:07 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org