From: Bob Copeland <me@bobcopeland.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: Nick Kossifidis <mick@madwifi-project.org>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
linville@tuxdriver.com, jirislaby@gmail.com
Subject: Re: [ath5k-devel] [PATCH 5/5] ath5k: Update reset code
Date: Tue, 3 Feb 2009 23:52:08 -0500 [thread overview]
Message-ID: <20090204045208.GA8086@hash.localnet> (raw)
In-Reply-To: <40f31dec0902030828v453fdeafh9d47a156c07f6c9d@mail.gmail.com>
On Tue, Feb 03, 2009 at 06:28:47PM +0200, Nick Kossifidis wrote:
> Nice catch ;-)
>
> Another difference i remembered is that we now don't set the TPC
> register to 3f (until we fix the whole tx power stuff). I'll try to
> reproduce this with my ar2425 as it turns it also has problems.
And the winning hunk is:
if (ah->ah_version != AR5K_AR5210) {
ath5k_hw_reg_write(ah, 0xffffffff, AR5K_PISR);
- /* If we later allow tuning for this, store into sc structure */
- data = AR5K_TUNE_RSSI_THRES |
- AR5K_TUNE_BMISS_THRES << AR5K_RSSI_THR_BMISS_S;
- ath5k_hw_reg_write(ah, data, AR5K_RSSI_THR);
}
(hmm, bmiss threshold, should've seen that before...)
With that reverted from the rest of the patchset, I no longer get the
interrupt storm. I do seem to get an occasional lockup at association
time, but I haven't caught an oops for that yet. It could be unrelated.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-02-04 4:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 2:31 [PATCH 5/5] ath5k: Update reset code Nick Kossifidis
2009-01-31 17:08 ` Bob Copeland
2009-01-31 18:48 ` [ath5k-devel] " Nick Kossifidis
2009-01-31 18:56 ` Felix Fietkau
2009-01-31 20:50 ` Nick Kossifidis
2009-01-31 21:45 ` Felix Fietkau
2009-01-31 22:38 ` Bob Copeland
2009-01-31 22:58 ` Nick Kossifidis
2009-02-01 4:41 ` Bob Copeland
2009-02-01 3:50 ` Nick Kossifidis
2009-02-01 4:05 ` Felix Fietkau
2009-02-01 4:50 ` Nick Kossifidis
2009-02-01 5:07 ` Felix Fietkau
2009-02-01 5:14 ` Nick Kossifidis
2009-02-03 16:24 ` Bob Copeland
2009-02-03 16:28 ` [ath5k-devel] " Nick Kossifidis
2009-02-04 4:52 ` Bob Copeland [this message]
2009-02-04 5:14 ` Nick Kossifidis
2009-02-04 6:58 ` Nick Kossifidis
2009-02-04 21:57 ` Nick Kossifidis
2009-02-05 15:51 ` Bob Copeland
2009-02-05 15:59 ` [ath5k-devel] " Maxim Levitsky
2009-02-05 21:06 ` Nick Kossifidis
2009-02-06 3:52 ` Bob Copeland
2009-02-07 5:03 ` Bob Copeland
2009-02-07 5:20 ` Nick Kossifidis
2009-02-07 14:39 ` Bob Copeland
2009-02-07 16:13 ` Nick Kossifidis
2009-02-08 17:56 ` John W. Linville
2009-02-08 18:01 ` Nick Kossifidis
2009-02-05 23:28 ` Nick Kossifidis
2009-02-06 3:50 ` Bob Copeland
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=20090204045208.GA8086@hash.localnet \
--to=me@bobcopeland.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mick@madwifi-project.org \
--cc=mickflemm@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.