From: Ike Panhc <ike.pan@canonical.com>
To: acpi4asus-user@lists.sourceforge.net,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Corentin Chary <corentincj@iksaif.net>, Matthew Garrett <mjg@redhat.com>
Subject: asus-laptop kill wifi when initital
Date: Thu, 09 Sep 2010 15:41:27 +0800 [thread overview]
Message-ID: <4C888FA7.9090402@canonical.com> (raw)
Hi,
I have a report[1] that user has to blacklist the asus-laptop otherwise wifi
can not work. I copied asus-laptop.c from 2.6.32 kernel and remove two
lines[2] that set WLED/BLED on. The modified driver works fine.
User uses 2.6.32 based kernel and when 2.6.34, a module parameter
"wifi_status" is added[3] to let user choose what he want to do on WLED/BLED
when initial. So I guess there are some reports tells the parameter for
WLED/BLED maybe changed. Since the default action is still on because some
machine need to enable WLED/BLED when booting. Any idea for the future
change? For example telling user add an options on /etc/modprobe.d, or try
to have a list of machine that not to set WLED/BLED to 1 when booting?
[1] http://launchpad.net/bugs/612454
[2] Patch is shown below:
@@ -1273,8 +1273,10 @@ static int asus_hotk_add(struct acpi_dev
asus_hotk_found = 1;
/* WLED and BLED are on by default */
+#if 0 /* Remove by Ike Panhc */
write_status(bt_switch_handle, 1, BT_ON);
write_status(wl_switch_handle, 1, WL_ON);
+#endif
/* If the h/w switch is off, we need to check the real status */
write_status(NULL, read_status(BT_ON), BT_ON);
[3] https://patchwork.kernel.org/patch/76283/
next reply other threads:[~2010-09-09 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 7:41 Ike Panhc [this message]
2010-09-09 7:52 ` asus-laptop kill wifi when initital Corentin Chary
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=4C888FA7.9090402@canonical.com \
--to=ike.pan@canonical.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentincj@iksaif.net \
--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