On Fri, Jun 19, 2009 at 1:00 PM, Andrey Yurovsky<andrey@xxxxxxxxxxx> wrote: > You'll want wireless-testing (or the latest compat), after commit > 41ba08509. However ath5k will not beacon until you issue a scan due > to a bug. By the way, I imagine this is a side effect of calling ath5k_beacon_config inside ath5k_reset(). If so, we probably want to call it at the appropriate time when the interface is brought up. I have been working on a patch to rework the beaconing, namely using bss_conf->enable_beacon and calling beacon_config whenever the beacon interval or beacon changes, that might fix it but I'm not too familiar with mesh details to say. -- 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
