From: joeyli <jlee@suse.com>
To: Ike Panhc <ike.pan@canonical.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, Matthew Garrett <mjg@redhat.com>,
Joey Lee <jlee@novell.com>
Subject: Re: [PATCH] acer-wmi: blacklist Thinkpad edge E520
Date: Tue, 25 Oct 2011 06:20:31 +0800 [thread overview]
Message-ID: <1319494831.17773.153.camel@linux-s257.site> (raw)
In-Reply-To: <4E9CE262.60601@canonical.com>
Hi Ike,
於 二,2011-10-18 於 10:20 +0800,Ike Panhc 提到:
> Hi Joey,
>
> On 10/18/2011 09:48 AM, joeyli wrote:
> > Hi Ike,
> >
> > Could you please attached on the "rfkill list" output when press Fn key?
> > Then we can check the rfkill status change.
>
> The output of rfkill list is at
> https://launchpadlibrarian.net/78485925/RfKill.txt
>
> .. and bug reporter tells me that he can not unblock wireless.
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836865/comments/0
>
> >
> > And,
> > Thinkpad E520 have AMW0 method and I thought acer-wmi query wrong EC
> > register address so your acer-wireless was always soft-blocked.
> >
> > Does it possible kindly help me to find out which register on E520 is
> > mapping to wireless status? Please reference to Carlos's acer_ec.pl
> > tool:
> >
> > http://code.google.com/p/aceracpi/wiki/EmbeddedController
> >
> > Simple use:
> > watch -n 1 perl acer_ec.pl regs
> >
> > Then press your wireless Fn key to monitor which register changed when
> > you press Fn key:
> >
> > e.g. the register at row B0 and column 0A is register 0xBA (0x is used
> > to indicate this is a hexadecimal number).
> >
> > There maybe have other EC register changing when you press key, please
> > do a couple of times and make sure you find out the right one.
> >
> > If we are lucky, we can find out one EC register mapping to your
> > wireless state.
>
> I've asked bug reporter to do so. Unfortunately nothing useful found.
>
> Please refer to the link below:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836865/comments/13
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836865/comments/14
>
> The full discussion is at
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836865
>
Bad!
I also didn't see useful things from DSDT, looks like the control
doesn't through EC.
Let's add this device to blacklist!
Thank's
Joey Lee
next prev parent reply other threads:[~2011-10-24 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 6:51 Ike Panhc
2011-10-13 16:35 ` joeyli
2011-10-14 2:48 ` Ike Panhc
2011-10-18 1:48 ` joeyli
2011-10-18 2:20 ` Ike Panhc
2011-10-24 22:20 ` joeyli [this message]
2011-10-24 22:22 ` joeyli
2011-10-24 23:13 ` Dave Jones
2011-10-25 2:57 ` Ike Panhc
2011-11-06 9:29 ` 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=1319494831.17773.153.camel@linux-s257.site \
--to=jlee@suse.com \
--cc=ike.pan@canonical.com \
--cc=jlee@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
/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
all inboxes | Powered by JetHome®