From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Drapko Nitzhonot <drapkos@gmail.com>,
linux-wireless@vger.kernel.org, Bob Copeland <me@bobcopeland.com>,
stable@kernel.org
Subject: Re: Status of http://patchwork.kernel.org/patch/56785/
Date: Mon, 1 Mar 2010 23:01:50 +0100 [thread overview]
Message-ID: <201003012301.51478.mb@bu3sch.de> (raw)
In-Reply-To: <20100301201214.GG2961@tuxdriver.com>
On Monday 01 March 2010 21:12:14 John W. Linville wrote:
> > An AP running 2.6.32 is unusable without those two patches.
> > However, it's rock stable as soon as those are applied.
>
> commit a951ae2176b982574ffa197455db6c89359fd5eb
> Author: Bob Copeland <me@bobcopeland.com>
> Date: Wed Jan 20 23:51:04 2010 -0500
>
> ath5k: fix setup for CAB queue
>
> The beacon sent gating doesn't seem to work with any combination
> of flags. Thus, buffered frames tend to stay buffered forever,
> using up tx descriptors.
>
> Instead, use the DBA gating and hold transmission of the buffered
> frames until 80% of the beacon interval has elapsed using the ready
> time. This fixes the following error in AP mode:
>
> ath5k phy0: no further txbuf available, dropping packet
>
> Add a comment to acknowledge that this isn't the best solution.
>
> Signed-off-by: Bob Copeland <me@bobcopeland.com>
> Acked-by: Nick Kossifidis <mickflemm@gmail.com>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
> commit 5d6ce628f986d1a3c523cbb0a5a52095c48cc332
> Author: Bob Copeland <me@bobcopeland.com>
> Date: Wed Jan 20 23:51:03 2010 -0500
>
> ath5k: dont use external sleep clock in AP mode
>
> When using the external sleep clock in AP mode, the
> TSF increments too quickly, causing beacon interval
> to be much lower than it is supposed to be, resulting
> in lots of beacon-not-ready interrupts.
>
> This fixes http://bugzilla.kernel.org/show_bug.cgi?id=14802.
>
> Signed-off-by: Bob Copeland <me@bobcopeland.com>
> Acked-by: Nick Kossifidis <mickflemm@gmail.com>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
Ok, so indeed, there was no CC to stable. I think these are critical patches
that should go into the stable tree.
--
Greetings, Michael.
next prev parent reply other threads:[~2010-03-01 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 20:18 Status of http://patchwork.kernel.org/patch/56785/ Drapko Nitzhonot
2010-02-27 20:24 ` Michael Buesch
2010-03-01 20:12 ` John W. Linville
2010-03-01 22:01 ` Michael Buesch [this message]
2010-03-02 12:57 ` 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=201003012301.51478.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=drapkos@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=me@bobcopeland.com \
--cc=stable@kernel.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 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.