From: "Bob Copeland" <me@bobcopeland.com>
To: Nick Kossifidis <mick@madwifi-project.org>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org
Cc: linville@tuxdriver.com, jirislaby@gmail.com, mcgrof@gmail.com,
nbd@openwrt.org
Subject: Re: [PATCH 5/5] ath5k: Update reset code
Date: Thu, 5 Feb 2009 10:51:52 -0500 [thread overview]
Message-ID: <20090205154532.M30551@bobcopeland.com> (raw)
In-Reply-To: <20090204215706.GA5651@makis>
On Wed, 4 Feb 2009 23:57:06 +0200, Nick Kossifidis wrote
> * Update reset and sync with HALs
> * Clean up eeprom settings and tweaking of initvals and put them on
separate functions
> * Set/Restore 32KHz ref clk operation
> * Add some more documentation
> TODO: Spur mitigation, tpc, half/quarter rate, compression etc
>
> v2: Address comments from Bob and Felix and fix RSSI threshold bug
> introduced on the first version of the patch
>
> Signed-Off-by: Nick Kossifidis <mickflemm@gmail.com>
This works much better, except I still get some hard hangs
occasionally. Doesn't appear to be bmiss storm this time. I did it
with a VT up and didn't get an oops; I guess I'll try a serial console
or some printks.
I could trigger it via a few suspend-resume cycles, so I guess it's the
reset from ath5k_init(). Did you still have any problems with the 2425?
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-02-05 15: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
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 [this message]
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=20090205154532.M30551@bobcopeland.com \
--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=mcgrof@gmail.com \
--cc=mick@madwifi-project.org \
--cc=nbd@openwrt.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).