From: Nicolas Cavallari <Nicolas.Cavallari@lri.fr>
To: Sujith Manoharan <sujith@msujith.org>
Cc: John Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3/3] ath9k: Fix IBSS joiner mode
Date: Tue, 12 Feb 2013 10:24:27 +0100 [thread overview]
Message-ID: <511A0A4B.6010507@lri.fr> (raw)
In-Reply-To: <1359972504-8900-3-git-send-email-sujith@msujith.org>
On 04/02/2013 11:08, Sujith Manoharan wrote:
> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> On joining an existing IBSS network, beaconing has to start
> only after a TSF sync has happened by receiving a beacon from
> the BSS. In creator mode, beaconing can start immediately after
> a HW reset has been done.
>
> Now that mac80211 notifies the driver of the mode type (creator/joiner)
> via ieee80211_bss_conf->ibss_creator, make use of it to properly setup
> the HW beacon timers.
>
> Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
> ---
Even though my IBSS network isn't as large as it was when i experienced
the most severe problems, i see no stuck beacon now; the network is much
more reliable.
Thanks.
Tested-by: Nicolas Cavallari <nicolas.cavallari@lri.fr>
next prev parent reply other threads:[~2013-02-12 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 10:08 [PATCH 1/3] ath9k: Print the negotiated HT capabilities Sujith Manoharan
2013-02-04 10:08 ` [PATCH 2/3] ath9k: Fix ATH9K_HW_CAP_HT usage Sujith Manoharan
2013-02-04 10:08 ` [PATCH 3/3] ath9k: Fix IBSS joiner mode Sujith Manoharan
2013-02-12 9:24 ` Nicolas Cavallari [this message]
2013-02-12 9:55 ` Sujith Manoharan
2013-02-08 14:08 ` [PATCH 1/3] ath9k: Print the negotiated HT capabilities Sujith Manoharan
2013-02-08 19:45 ` John W. Linville
2013-02-09 2:27 ` Sujith Manoharan
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=511A0A4B.6010507@lri.fr \
--to=nicolas.cavallari@lri.fr \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sujith@msujith.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.