From: Ike Panhc <ike.pan@canonical.com>
To: joeyli <jlee@suse.com>
Cc: Carlos Corbacho <carlos@strangeworlds.co.uk>,
mjg@redhat.com, platform-driver-x86@vger.kernel.org,
Dmitry Torokhov <dtor@mail.ru>,
Corentin Chary <corentincj@iksaif.net>,
Thomas Renninger <trenn@suse.de>
Subject: Re: [PATCH] acer-wmi: check wireless capability on AMW0_GUID2 machines
Date: Thu, 12 Jan 2012 00:54:06 +0800 [thread overview]
Message-ID: <4F0DBEAE.4010707@canonical.com> (raw)
In-Reply-To: <1326255999.16788.40.camel@linux-s257.site>
On 01/11/2012 12:26 PM, joeyli wrote:
> 於 一，2012-01-09 於 22:15 +0000，Carlos Corbacho 提到：
>> 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 think this
>> involved Acer hardware, but this was some time ago...) where the wireless
>> detection wasn't working with this, but if we forced it on, it worked fine.
>>
>
> 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 RF
> state if we are lucky.
>
> Unfortunately, direct enable wireless capability causes some non-acer
> machines' wireless rfkill always disabled. e.g. Lenovo E520
>
> https://bugzilla.redhat.com/show_bug.cgi?id=674353
>
> If we don't check the wireless capability, then they need manually add
> acer-wmi to backlist. On some lenovo machines, ideapad-laptop driver
> should support by lenovo's ACPI method.
>
I've got two reports which says after poking the ec register, the phy0 rfkill reports hard blocked by mistake. And few hours ago I get the third report says the similar issue. I will summary the report.
I am thinking about alternative way
Since we have thinkpad_acpi and ideapad_laptop, both of them have rfkill capability. If there is VPC2004/IBM0068/LEN0068 in DSDT, then it will be fine if we do not register rfkill in acer-wmi.
Any thought?
next prev parent reply other threads:[~2012-01-11 16:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 6:31 [PATCH] acer-wmi: check wireless capability on AMW0_GUID2 machines Lee, Chun-Yi
2012-01-09 8:01 ` Carlos Corbacho
2012-01-09 10:00 ` joeyli
2012-01-09 22:15 ` Carlos Corbacho
2012-01-11 4:26 ` joeyli
2012-01-11 16:54 ` Ike Panhc [this message]
2012-01-12 0:21 ` joeyli
2012-01-25 1:18 ` Ike Panhc
2012-01-20 2:44 ` joeyli
2012-01-25 1:29 ` Ike Panhc
2012-01-25 1:57 ` [PATCH] acer-wmi: No wifi rfkill on Lenovo machines Ike Panhc
2012-01-25 2:14 ` Ike Panhc
2012-01-26 2:53 ` joeyli
2012-02-03 8:46 ` [PATCH v2] " Ike Panhc
2012-02-03 8:55 ` Ike Panhc
2012-02-06 9:55 ` joeyli
2012-02-11 19:10 ` Jonathan Nieder
2012-02-21 9:22 ` [PATCH resend] " Jonathan Nieder
2012-03-14 21:53 ` [PATCH 3.0.y] " Jonathan Nieder
2012-03-14 22:02 ` Greg KH
2012-03-14 22:17 ` Jonathan Nieder
2012-03-16 4:03 ` Ike Panhc
2012-03-16 6:11 ` joeyli
2012-03-16 17:20 ` Greg KH
2012-03-19 2:08 ` joeyli
2012-03-19 12:40 ` Andrey
2012-03-19 14:48 ` Jonathan Nieder
2012-01-24 0:04 ` [PATCH] acer-wmi: check wireless capability on AMW0_GUID2 machines joeyli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F0DBEAE.4010707@canonical.com \
--to=ike.pan@canonical.com \
--cc=carlos@strangeworlds.co.uk \
--cc=corentincj@iksaif.net \
--cc=dtor@mail.ru \
--cc=jlee@suse.com \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=trenn@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox