From: Carlos Corbacho <carlos@strangeworlds.co.uk>
To: Jarod Wilson <jarod@redhat.com>
Cc: aceracpi@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acer-wmi: don't bother loading on unsupported systems
Date: Mon, 6 Apr 2009 20:53:11 +0100 [thread overview]
Message-ID: <200904062053.12303.carlos@strangeworlds.co.uk> (raw)
In-Reply-To: <200904060940.16889.jarod@redhat.com>
On Monday 06 April 2009 14:40:16 Jarod Wilson wrote:
> So have acer-wmi just bail on unsupported systems -- includes only my
> particular model of the Aspire One atm, but a larger list of unsupported
> systems can be found here:
>
> http://code.google.com/p/aceracpi/wiki/SupportedHardware
>
> This might well become unnecessary once the WMI sysfs interface mentioned
> in acer-wmi.c exists and the wild-card dmi modalias is gone, but for now...
> I prefer to have working wireless, and this isn't exactly an obvious root
> cause. I lack the hardware to further extend the blacklist, but doing so is
> trivial. Whether or not loading acer-wmi actually negatively impacts
> machines other than the AAO is unknown at this time.
NAK.
An equivalent patch to this was submitted to the ACPI tree two days ago (which
blacklists both the known Aspire One DMI entries) and is now upstream (and
will also be backported to the next stable release).
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a74dd5fdabcd34c93e17e9c7024eeb503c92b048
(The Aspire One is special as, unlike other Acer laptops which are
unsupported, it provides the ACPI-WMI inteface we're trying to match on, so it
really does have to be blacklisted - so WMI matching won't help in this
particular case).
-Carlos
--
E-Mail: carlos@strangeworlds.co.uk
Web: strangeworlds.co.uk
GPG Key ID: 0x23EE722D
next prev parent reply other threads:[~2009-04-06 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 13:40 Jarod Wilson
2009-04-06 19:53 ` Carlos Corbacho [this message]
2009-04-06 20:04 ` Jarod Wilson
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=200904062053.12303.carlos@strangeworlds.co.uk \
--to=carlos@strangeworlds.co.uk \
--cc=aceracpi@googlegroups.com \
--cc=jarod@redhat.com \
--cc=linux-kernel@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®