From: Dan Williams <dcbw@redhat.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath5k: enable RXing beacons
Date: Sun, 02 Nov 2008 20:39:13 -0500 [thread overview]
Message-ID: <1225676353.13684.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1225672612-15106-1-git-send-email-lrodriguez@atheros.com>
On Sun, 2008-11-02 at 16:36 -0800, Luis R. Rodriguez wrote:
> Prior to this we would rely only on probe responses
> from the AP to keep associated. We now receive beacons
> on ath5k. This should fix sporadic disassociations.
>
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Is this also a candidate for -stable?
> ---
> drivers/net/wireless/ath5k/base.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/ath5k/base.c b/drivers/net/wireless/ath5k/base.c
> index f5f46fe..5505f45 100644
> --- a/drivers/net/wireless/ath5k/base.c
> +++ b/drivers/net/wireless/ath5k/base.c
> @@ -2948,6 +2948,8 @@ static void ath5k_configure_filter(struct ieee80211_hw *hw,
> AR5K_RX_FILTER_PROBEREQ | AR5K_RX_FILTER_PROM;
> if (sc->opmode != NL80211_IFTYPE_STATION)
> rfilt |= AR5K_RX_FILTER_PROBEREQ;
> + if (sc->opmode == NL80211_IFTYPE_STATION)
> + rfilt |= AR5K_RX_FILTER_BEACON;
> if (sc->opmode != NL80211_IFTYPE_AP &&
> sc->opmode != NL80211_IFTYPE_MESH_POINT &&
> test_bit(ATH_STAT_PROMISC, sc->status))
next prev parent reply other threads:[~2008-11-03 1:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 0:36 [PATCH] ath5k: enable RXing beacons Luis R. Rodriguez
2008-11-03 1:39 ` Dan Williams [this message]
2008-11-03 2:10 ` Bob Copeland
2008-11-03 4:43 ` Luis R. Rodriguez
2008-11-03 4:49 ` Luis R. Rodriguez
2008-11-03 4:52 ` Luis R. Rodriguez
2008-11-03 15:17 ` Bob Copeland
2008-11-04 12:37 ` Bob Copeland
2008-11-04 19:19 ` Luis R. Rodriguez
2008-11-05 16:03 ` Bob Copeland
2008-11-05 16:32 ` Nick Kossifidis
2008-11-03 10:16 ` Felix Fietkau
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=1225676353.13684.2.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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.