linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ike Panhc <ike.pan@canonical.com>
To: Dave Jones <davej@redhat.com>, joeyli <jlee@suse.com>,
	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 10:57:36 +0800	[thread overview]
Message-ID: <4EA625A0.6090909@canonical.com> (raw)
In-Reply-To: <20111024231329.GA25993@redhat.com>

On 10/25/2011 07:13 AM, Dave Jones wrote:
> On Tue, Oct 25, 2011 at 06:22:47AM +0800, joeyli wrote:
>  > 於 四,2011-10-13 於 14:51 +0800,Ike Panhc 提到:
>  > > BugLink: http://launchpad.net/bugs/836865
>  > > BugLink: http://launchpad.net/bugs/826784
>  > > 
>  > > There are reports say that acer-wmi is loaded on Thinkpad E520 which
>  > > cause wireless connection hard blocked and we can not unblock it. It
>  > > will be better not to load acer-wmi on this machine.
>  > > 
>  > > Signed-off-by: Ike Panhc <ike.pan@canonical.com>
>  > > ---
>  > >  drivers/platform/x86/acer-wmi.c |    7 +++++++
>  > >  1 files changed, 7 insertions(+), 0 deletions(-)
>  > > 
>  > > diff --git a/drivers/platform/x86/acer-wmi.c b/drivers/platform/x86/acer-wmi.c
>  > > index af2bb20..dc9a116 100644
>  > > --- a/drivers/platform/x86/acer-wmi.c
>  > > +++ b/drivers/platform/x86/acer-wmi.c
>  > > @@ -325,6 +325,13 @@ static struct dmi_system_id __devinitdata acer_blacklist[] = {
>  > >  			DMI_MATCH(DMI_PRODUCT_NAME, "AOA150"),
>  > >  		},
>  > >  	},
>  > > +	{
>  > > +		.ident = "Lenovo Thinkpad Edge E520",
>  > > +		.matches = {
>  > > +			DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
>  > > +			DMI_MATCH(DMI_PRODUCT_NAME, "114320U"),
>  > > +		},
>  > > +	},
>  > >  	{}
>  > >  };
>  > >  
>  > 
>  > Unfortunately didn't see any useful EC register for unblock wifi rfkill in acer-wmi, let's 
>  > add this device to blacklist.
>  > 
>  > Signed-off-by: Lee, Chun-Yi <jlee@novell.com>
> 
> We've seen similar reports from other Lenovo machines & acer-wmi in Fedora bugzilla.
> https://bugzilla.redhat.com/show_bug.cgi?id=674353 for example has people reporting
> the b450 and V460 also suffer the same issue.
> 
> (There are also a bunch of bug reports from the other *-wmi modules on various hardware.
> It seems these modules really upset rfkill).
> 
> 	Dave
> 

I've tried to find a way to prevent acer-wmi loaded if VPC2004 found in DSDT. Thinking twice, seems to do this in kernel is not a good idea because if acer-wmi is necessary in one model of ideapads then we need to re-compile kernel for testing. I think it will be better to do this in udev if possible.

  reply	other threads:[~2011-10-25  2:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13  6:51 [PATCH] acer-wmi: blacklist Thinkpad edge E520 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
2011-10-24 22:22 ` joeyli
2011-10-24 23:13   ` Dave Jones
2011-10-25  2:57     ` Ike Panhc [this message]
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=4EA625A0.6090909@canonical.com \
    --to=ike.pan@canonical.com \
    --cc=davej@redhat.com \
    --cc=jlee@novell.com \
    --cc=jlee@suse.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;
as well as URLs for NNTP newsgroup(s).