On Wed, Aug 19, 2009 at 7:33 PM, Javier Cardona<javier@xxxxxxxxxxx> wrote:
> Hi,
>
> Could someone familiar with the ath9k help us solve a problem with
> mesh beaconing?
I am not too familiar with ath9k, but I would suspect that
there's an ordering issue with when enable_beacon is recognized,
so beaconing doesn't start until the next reset() is called.
E.g. this fix for ath5k sounds similar:
commit 9718512d81a7f7bd0166d1e033f8395022ecb2e9
Author: Bob Copeland <me@xxxxxxxxxxxxxxx>
Date: Wed Jul 29 10:29:03 2009 -0400
ath5k: update PCU opmode whenever a new interface is added
--
Bob Copeland %% www.bobcopeland.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
