On Fri, Jul 20, 2012 at 5:26 AM, AceLan Kao wrote:
> If the user bit is set, that mean BIOS can't set and record the wlan
> status, it will report the value read from id ASUS_WMI_DEVID_WLAN_LED
> while we query the wlan status by id ASUS_WMI_DEVID_WLAN through WMI.
> So, we have to record wlan sta
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 turn on/off the wireless LED explicitly.
But I found there is another wireless LED bug in launchpad and which is
not in the wapf=4 quirk.
So
If the user bit is set, that mean BIOS can't set and record the wlan
status, it will report the value read from id ASUS_WMI_DEVID_WLAN_LED
while we query the wlan status by id ASUS_WMI_DEVID_WLAN through WMI.
So, we have to record wlan status in id ASUS_WMI_DEVID_WLAN_LED
while setting the wlan sta
On Thursday, July 19, 2012, Len Brown wrote:
>
> > The patchset has been tested on Toshiba Portege R500 and more testing is in
> > the works. If there are no objections, I'd like to push if for 3.6 through
> > the linux-pm tree.
>
> Good plan. Would need to merge w/ my tree only if we run into
