於 四，2011-06-09 於 16:36 +0800，Ike Panhc 提到：
> On 06/07/2011 09:48 PM, Joey Lee wrote:
> > 於 五，2011-06-03 於 14:49 +0200，Florian Heyer 提到：
> >> fn+f5 doesn't do anything no matter what state the wifi switch is.
> >> Personally i wouldn't mind if only the wifi switch is supported, i mean,
> >> you don't need a key combination if you have a real switch for wifi
> >> (de)activation.
> >>
> >
> > I thought need to check with Ike for more detail why the Fn+F5 key not
> > work on S205.
>
But Florian said the Fn+F5 doesn't work to him, as you said, the _Q2B
works when GWSS is not zero:
Method (_Q2B, 0, NotSerialized) /* wifi key? */
{
Store (0x2B, P80H)
If (LEqual (GWSS, 0x00)) {} /* on issue machine, GWSS is 0
*/
Else
{
If (WLPS) /* if have wireless */
{
Store (WRST, WLEN) /* write wireless RF state to
EC */
}
> I read the DSDT again. Fn+F5 is the soft rfkill key. It looks fine.
> I guess the problem is the hard rfkill status is blocked, wifi will be
> blocked even the soft one is unblocked.
>
> > As I know on Thinkpad machine, the hardware switch causes killswitch set
> > to hard-block, and Fn+F5 causes killswitch set to soft-block.
> >
> > Ike,
> > need your comments for Fn+F5 key and wireless hardware switch on
> > ideapad. How does it implement on ideapad?
> > - press Fn+F5: soft-block wireless killswitch?
> > - wireless hardware switch: hard-block wireless killswitch?
>
> Both of the answers are yes.
>
> The problem is that on ideapad s205 without acer-wmi, when ideapad-laptop
> have the hard switch event, the driver asks the status of switch and DSDT
> replies blocked.
>
> In the DSDT the driver read bit of GWSS as status of hardware switch and
> I can not find out anything to update GWSS in DSDT :(
I also didn't see any other statement in DSDT touch GWSS.
On the other hand,
I reviewed Florian's following mail:
於 二，2011-05-31 於 15:02 +0200，Florian Heyer 提到：
> On 05/31/2011 11:42 AM, Joey Lee wrote:
> > Just checked your DSDT, it declared the AMW0 methods, I agreed Ike's
> > suggestion that will be better you direct test acer-wmi on your machine.
> >
> > Please modprobe acer-wmi driver, then try to turn on/off bluetooth or
> > wireless device by rfkill.
>
> Hello Joey,
>
> here are some findings with acer_wmi. I execute the following steps from
> top to bottom, and only after the last step my wifi works. After each
> step you find the output of "rfkill list":
>
> after booting (no ideapad_laptop, no acer_wmi):
> 0: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 1: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: yes
>
When system boot, wireless is hard blocked by default.
> after loading acer_wmi (wifi switch is on):
> 0: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
> 1: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> 2: acer-wireless: Wireless LAN
> Soft blocked: yes
> Hard blocked: no
The acer-wmi will set initial value by call AMW0 wmi method to unblock wireless.
>
> after switching off:
> 1: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> 2: acer-wireless: Wireless LAN
> Soft blocked: yes
> Hard blocked: no
>
Press hardware switch to off, here have a question:
+ It disabled bluetooth but not wireless?
I thought the wireless works fine when system at this status, even acer-wireless
stay on soft blocked.
> switching on again:
> 1: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: yes
> 2: acer-wireless: Wireless LAN
> Soft blocked: yes
> Hard blocked: no
> 3: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
>
Press hardware switch again, here have a question:
+ looks like it enable bluetooth but hard blocked wireless again?
>
> after removing acer_wmi with modprobe -r:
> 1: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> 3: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
>
Here a bit not make sense:
+ acer-wmi doesn't touch wireless by AMW0 when it un-probe, but wireless state
set to unblock.
Does that mean current "hardware switch" state is "OFF", but wireless state
is unblock?
>
>
> Now wifi networking can be used!
> The optimal solution would be to have ideapad_laptop make all
> initialisations so wifi can be used after booting with no manual steps
> necessary.
>
> Regards
Here have some questions:
+ Does "hardware switch" on IdeaPad S205 not just control wireless? Does it
also control bluetooth?
+ Does "hardware switch" emit any KEY_WIRELESS, KEY_BLUETOOTH or KEY_RFKILL?
And rfkill-input works?
I mean: Does this switch only control by BIOS? or actually rfkill-input also
touch the killswitch?
Thank's a lot!
Joey Lee
--
To unsubscribe from this list: send the line "unsubscribe platform-driver-x86"
in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
