On Wed, Jun 3, 2009 at 12:59 PM, Nick Kossifidis <mickflemm@xxxxxxxxx> wrote: > 2009/6/3 Andrey Yurovsky <andrey@xxxxxxxxxxx>: >> On Wed, Jun 3, 2009 at 11:21 AM, Nick Kossifidis <mickflemm@xxxxxxxxx> wrote: >>> 2009/6/2 Andrey Yurovsky <andrey@xxxxxxxxxxx>: >>>> With wireless-testing from a couple of days ago, an X86 system, and this patch: >>>> http://osdir.com/ml/linux-wireless/2009-05/msg01241.html >>>> ath9k can bring up a mesh point interface and doesn't crash for me, >>>> but there are no mesh beacons, so mesh isn't working. On ath5k, there >>>> are also no beacons and mesh doesn't work, but there's no crash. >>>> >>> >>> >>> Hmm, try adding NL80211_IFTYPE_MESH_POINT here -> >>> >>> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob;f=drivers/net/wireless/ath/ath5k/pcu.c;h=ec35503f6a40e6b6a1cc4323287b31e7cdd3a428;hb=HEAD#l733 >> >> It's already there, in ath5k_hw_set_opmode. We'll need to trace >> what's going on and see why we don't get beacons. Last night I had an >> ath5k MP suddenly start beaconing but I haven't been able to reproduce >> that yet. > > 736 /* When in AP mode zero timer0 to start TSF */ > 737 if (ah->ah_op_mode == NL80211_IFTYPE_AP) > 738 ath5k_hw_reg_write(ah, 0, AR5K_TIMER0); > > We need to do this for NL80211_IFTYPE_MESH_POINT or DBA won't fire up > and beacon queue wont start... Thanks Nik, that gets beaconing going but only after a issuing a scan (we have the same problem on rt2x00). > -- > GPG ID: 0xD21DB2DB > As you read this post global entropy rises. Have Fun ;-) > Nick > -- 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
