From: "Bob Copeland" <me@bobcopeland.com>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linville@tuxdriver.com, jirislaby@gmail.com,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org
Subject: Re: [ath5k-devel] [PATCH 0/6] ath5k: various misc fixes
Date: Thu, 22 Jan 2009 10:29:38 -0500 [thread overview]
Message-ID: <20090122152204.M73296@bobcopeland.com> (raw)
In-Reply-To: <1232637118.19795.3.camel@maxim-laptop>
On Thu, 22 Jan 2009 17:11:58 +0200, Maxim Levitsky wrote
> On Thu, 2009-01-22 at 08:44 -0500, Bob Copeland wrote:
> > Hi, here are some various updates for ath5k, some minor fixes, it's
> > probably all 2.6.30 material.
> >
> > - patch 1 fixes a locking bug, but for consistency, not to fix any reported
> > issue
> > - patches 2 and 4 are cleanups
> > - patch 3 makes reset() more closely match the HAL, it may help with reset
> > errors but really is unlikely to fix any problem
> > - patches 5 and 6 add missing support for some rate flags that have been
> > ignored by ath5k since forever
>
> I tried using those 4 patches that were your attempt to fix hangs
> the first one, probably helps a bit, but with them I got those 'failed
> to wakeup PHY' errors that persist even after suspend/resume cycle.
>
> Now I only use the 'continue reset sequence' and while chip locks up
> from time to time, I don't see the messages about failed PHY wakeup.
Cool, thanks for the feedback. For the record that is patch 3 in this
series. I sent everything except the one that puts a spinlock around
reset; that still hangs for me so I'd rather not send it until I know
why. Consequently, the other 2 patches (1 and 2) don't have any major
effect.
I suspect patch 3 helps but doesn't cure anything.
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2009-01-22 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 13:44 [PATCH 0/6] ath5k: various misc fixes Bob Copeland
2009-01-22 15:11 ` [ath5k-devel] " Maxim Levitsky
2009-01-22 15:29 ` Bob Copeland [this message]
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=20090122152204.M73296@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=maximlevitsky@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 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).