Ivo van Doorn wrote: > On Sunday 15 March 2009, Antonio Marques wrote: >> Upon further investigation, beaconing does not work after configuring >> an interface in mesh point mode but running 'iwlist mesh scan' >> triggers something in the driver that enables beaconing. >> After executing this command beacons are generated and correctly >> received at other nodes. > > Thats odd, but very interesting :) > Could you enable debugfs and CONFIG_RT2X00_LIB_DEBUGFS and > use the script from http://kernel.org/pub/linux/kernel/people/ivd/tools/rt2x00_regdump.sh > to create a register dump before running 'iwlist mesh scan' and afterwards. > (So basically when beaconing is broken and when it is working). > > Thanks, > > Ivo I get identical behavior with the patch I'm about to RFC for ath9k to enable mesh mode. I just want to test that it works with my b43, rt61pci, and rt2x00usb devices. Of the 4, ONLY b43 enables beaconing for mesh mode on interface up. I suspect my ath5k one will exhibit similar behavior. I've reviewed the b43 code about 100 times during the writing of my patch for ath9k and I can't spot what it's doing that's so different. Pat -- 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
