From: Bob Copeland <me@bobcopeland.com>
To: Richard Zidlicky <rz@linux-m68k.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: 2.6.31.[12] ath5k regression
Date: Sat, 10 Oct 2009 08:58:24 -0400 [thread overview]
Message-ID: <20091010125824.GA18841@hash.localnet> (raw)
In-Reply-To: <20091009143922.GA7848@linux-m68k.org>
On Fri, Oct 09, 2009 at 04:39:22PM +0200, Richard Zidlicky wrote:
> - ret = ath5k_hw_reset(ah, sc->opmode, sc->curchan, true);
> + ret = ath5k_hw_reset(ah, sc->opmode, sc->curchan, chan != NULL);
> if (ret) {
> ATH5K_ERR(sc, "can't reset hardware (%d)\n", ret);
> goto err;
So, this change effectively just ensures we now program the pcu registers
at startup (every other time chan should not be null). So my guess is
programming the pcu actually causes some problem. Can you try this patch
instead?
Also, since you're using adhoc there may be a path that's somewhat
different from infrastructure mode, please check dmesg after applying the
patch and be sure that you only see "ath5k: reset with change_channel=true"
once per driver load.
diff --git a/drivers/net/wireless/ath/ath5k/initvals.c b/drivers/net/wireless/ath/ath5k/initvals.c
index 8fa4393..c099fa2 100644
--- a/drivers/net/wireless/ath/ath5k/initvals.c
+++ b/drivers/net/wireless/ath/ath5k/initvals.c
@@ -1376,9 +1376,8 @@ static void ath5k_hw_ini_registers(struct ath5k_hw *ah, unsigned int size,
for (i = 0; i < size; i++) {
/* On channel change there is
* no need to mess with PCU */
- if (change_channel &&
- ini_regs[i].ini_register >= AR5K_PCU_MIN &&
- ini_regs[i].ini_register <= AR5K_PCU_MAX)
+ if (ini_regs[i].ini_register >= AR5K_PCU_MIN &&
+ ini_regs[i].ini_register <= AR5K_PCU_MAX)
continue;
switch (ini_regs[i].ini_mode) {
diff --git a/drivers/net/wireless/ath/ath5k/reset.c b/drivers/net/wireless/ath/ath5k/reset.c
index 3dab3d8..4b8ccbe 100644
--- a/drivers/net/wireless/ath/ath5k/reset.c
+++ b/drivers/net/wireless/ath/ath5k/reset.c
@@ -880,6 +880,9 @@ int ath5k_hw_reset(struct ath5k_hw *ah, enum nl80211_iftype op_mode,
ATH5K_TRACE(ah->ah_sc);
+ if (!change_channel)
+ printk(KERN_DEBUG "ath5k: reset with change_channel=true\n");
+
s_ant = 0;
ee_mode = 0;
staid1_flags = 0;
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-10-10 12:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 13:49 kernel crashes, 2.6.30, rt2x00, ath5k, ieee80211_get_*_rate, automatic rate control Richard Zidlicky
2009-06-21 18:04 ` Bob Copeland
2009-06-21 20:38 ` Richard Zidlicky
2009-06-22 20:15 ` Richard Zidlicky
2009-06-23 17:46 ` Richard Zidlicky
2009-06-23 20:25 ` Bob Copeland
2009-06-25 8:36 ` Richard Zidlicky
2009-07-05 12:31 ` Bob Copeland
2009-09-28 22:23 ` ath5k, wifi enable hotkeys Richard Zidlicky
2009-10-09 14:39 ` 2.6.31.[12] ath5k regression Richard Zidlicky
2009-10-10 12:58 ` Bob Copeland [this message]
2009-10-10 13:31 ` Bob Copeland
2009-10-11 12:26 ` Richard Zidlicky
2009-10-11 13:30 ` Bob Copeland
2009-10-11 22:00 ` Richard Zidlicky
2009-10-11 22:23 ` Bob Copeland
2009-10-12 20:23 ` Richard Zidlicky
2009-10-12 23:54 ` Bob Copeland
2009-10-13 19:37 ` Richard Zidlicky
2009-12-06 9:49 ` Richard Zidlicky
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=20091010125824.GA18841@hash.localnet \
--to=me@bobcopeland.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rz@linux-m68k.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).