From: Michael Buesch <mb@bu3sch.de>
To: Bob Copeland <me@bobcopeland.com>
Cc: linville@tuxdriver.com, jirislaby@gmail.com, mickflemm@gmail.com,
lrodriguez@atheros.com, linux-wireless@vger.kernel.org,
ath5k-devel@lists.ath5k.org
Subject: Re: [PATCH 0/2] ath5k AP mode fixes
Date: Thu, 21 Jan 2010 23:15:21 +0100 [thread overview]
Message-ID: <201001212315.21908.mb@bu3sch.de> (raw)
In-Reply-To: <1264049464-12292-1-git-send-email-me@bobcopeland.com>
On Thursday 21 January 2010 05:51:02 Bob Copeland wrote:
> Here are a couple of fixes to ath5k AP mode that have been
> kicking around for a bit.
>
> The sleep clock is disabled by legacy HAL for AP mode and at
> least one person had beaconing issues as a result of our not
> also doing so.
>
> Although we decided 'fix setup for CAB queue' was not ideal,
> there's no alternative at the moment and the current setup is
> causing problems for people, so IMO we should just take this
> patch as-is for now.
>
> Bob Copeland (2):
> ath5k: dont use external sleep clock in AP mode
> ath5k: fix setup for CAB queue
Thanks a lot for these, Bob. I'll test them on my AP.
Important: Please also add CC:stable to the patches to make
sure they reach the endusers for 2.6.32.x.
2.6.32.x currently is unusable in AP mode, so these patches
are pretty important fixes (if they actually fix the issues.
But I assume that for now ;) )
--
Greetings, Michael.
prev parent reply other threads:[~2010-01-21 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 4:51 [PATCH 0/2] ath5k AP mode fixes Bob Copeland
2010-01-21 4:51 ` [PATCH 1/2] ath5k: dont use external sleep clock in AP mode Bob Copeland
2010-01-21 11:29 ` Nick Kossifidis
2010-01-21 4:51 ` [PATCH 2/2] ath5k: fix setup for CAB queue Bob Copeland
2010-01-21 11:31 ` Nick Kossifidis
2010-01-21 22:15 ` Michael Buesch [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=201001212315.21908.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=me@bobcopeland.com \
--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 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).