於 四，2011-06-16 於 17:58 +0800，Ike Panhc 提到：
> On 06/15/2011 05:32 PM, Joey Lee wrote:
> > 於 四，2011-06-09 於 16:36 +0800，Ike Panhc 提到：
> >
> > 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 see your point. IMHO this is ok. When the radio switch is off, it shall
> be no different on every soft block modes.
> > 於 二，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.
> >
>
> Read the reply mail from Florian. This is a problem because hard blocked
> shall be no when the radio switch is on. Since phy0 is registered by wifi
> driver, I think this is not generic design.
>
There have some problems not just check the EC register then set
killswitch to hard blocked:
+ Per Florian's report, looks like the hardware key cann't unblock for
wireless and need acer-wmi driver unblock by evaluate AMW0 method. Does
that mean acer-wmi driver need evaluate AMW0 every time when user press
hardware key? This logic is so specially, and only S205 need do that.
+ The hardware key is not just control wireless, it also control
bluetooth. That will be better we also find out which EC register
mapping to bluetooth.
+ In current acer-wmi driver, it only maintain soft block for wireless
killswitch. IdeaPad S205 will be the only one machine that maintain hard
block but no soft block. There have no other acer machine like this.
Simply said, I don't want to put this specially case to acer-wmi (I
believe need use quirk). Does it possible support it in ideapad-laptop?
May I just check if there have VPC2004 device in dsdt, then acer-wmi
will not loading, leave ideapad-laptop take care?
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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
