From mboxrd@z Thu Jan 1 00:00:00 1970 From: joeyli Subject: Re: [PATCH] acer-wmi: check wireless capability on AMW0_GUID2 machines Date: Tue, 24 Jan 2012 08:04:25 +0800 Message-ID: <1327363465.7090.0.camel@linux-s257.site> References: <1326090677-25942-1-git-send-email-jlee@suse.com> <3474148.WRXZ4siLlh@valkyrie> <1326103224.24116.282.camel@linux-s257.site> <4607313.aZXtt4raMe@valkyrie> <1326255999.16788.40.camel@linux-s257.site> <4F0DBEAE.4010707@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from victor.provo.novell.com ([137.65.250.26]:35926 "EHLO victor.provo.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755380Ab2AXAIs (ORCPT ); Mon, 23 Jan 2012 19:08:48 -0500 In-Reply-To: <4F0DBEAE.4010707@canonical.com> Sender: platform-driver-x86-owner@vger.kernel.org List-ID: To: Ike Panhc Cc: Carlos Corbacho , mjg@redhat.com, platform-driver-x86@vger.kernel.org, Dmitry Torokhov , Corentin Chary , Thomas Renninger Hi Ike,=20 On Thu, 2012-01-12 at 00:54 +0800, Ike Panhc wrote: > On 01/11/2012 12:26 PM, joeyli wrote: > > =E6=96=BC =E4=B8=80=EF=BC=8C2012-01-09 =E6=96=BC 22:15 +0000=EF=BC=8C= Carlos Corbacho =E6=8F=90=E5=88=B0=EF=BC=9A > >> On Monday 09 Jan 2012 18:00:24 joeyli wrote: > >>> I just checked and found I also have no AMW0_GUID2 machines on my= hand, > >>> now. > >>> I have some questions about AMW0_GUID2: > >>> > >>> + Why we enabled wireless capability in acer-wim if a non-acer = machine has > >>> AMW0_GUID2 ? > >> > >> IIRC, there were some bug reports on non-Acer hardware (I don't th= ink this=20 > >> involved Acer hardware, but this was some time ago...) where the w= ireless=20 > >> detection wasn't working with this, but if we forced it on, it wor= ked fine. > >> > >=20 > > Yes, in acer-wmi supported some non-acer machine by quirk and read = EC > > register. That means we need find out EC register reflect to wifi R= =46 > > state if we are lucky. > >=20 > > Unfortunately, direct enable wireless capability causes some non-ac= er > > machines' wireless rfkill always disabled. e.g. Lenovo E520 > >=20 > > https://bugzilla.redhat.com/show_bug.cgi?id=3D674353=20 > >=20 > > If we don't check the wireless capability, then they need manually = add > > acer-wmi to backlist. On some lenovo machines, ideapad-laptop drive= r > > should support by lenovo's ACPI method. > >=20 >=20 > I've got two reports which says after poking the ec register, the phy= 0 rfkill reports hard blocked by mistake. And few hours ago I get the t= hird report says the similar issue. I will summary the report. >=20 Could you please share the above 3 reports and acpidump? Thanks Joey Lee > I am thinking about alternative way >=20 > Since we have thinkpad_acpi and ideapad_laptop, both of them have rfk= ill capability. If there is VPC2004/IBM0068/LEN0068 in DSDT, then it wi= ll be fine if we do not register rfkill in acer-wmi. >=20 > Any thought? >=20