On 4 October 2011 23:26, Christian Lamparter <chunk...@googlemail.com> wrote: > On Tuesday, October 04, 2011 04:50:42 PM Adrian Chadd wrote: >> Also whilst I'm at it, "SPECTRUM_MANAGEMENT" is a very broad flag to set. > > Hm, 802.11-2007 5.4.4 "Spectrum management services" explicitly > mentions that both services TPC and DFS are required in some > regulatory domains for operation in the 5 GHz band.
Right, but just for hostap mode, correct? I'm also thinking about non-hostap mode support. > [ Just for fun: Do you know how the AR5418 handled radars in > the proprietary turbo mode in the 5 GHz band? And how does > Atheros own driver/stack/etc. deals with this limitation? > After all Unex sold/sells the DNBA-81 on their product page > as: <http://www.unex.com.tw/product/dnba-81> > > "DNBA-81 is a 802.11n 2x3 2-stream a/b/g dual band wifi > Cardbus designed specifically for laptops and *access points*/ > home gateways/consumer electronics/multimedia entertainment > devices/peripherals with standard Cardbus slot." ] I haven't sat down and looked at exactly what the AR5416/AR5418 support is like save what I've seen when digging into the meaning behind the extended EEPROM bits. In any case, the easiest solution is to just disable HT40 for those (which, incidentally, is exactly what FreeBSD's ath and net80211 regulatory code did until recently.) And as I said, that isn't needed for station mode operation, so you can just use HT/40 channels. :) Besides, you realise that vendors say the darnest things at times? :) For example, one well-known vendor lists their AR9160 NICs as DFS ready (and thus people who buy them think they're DFS ready), but if you buy some of their MIPS SOC hardware, they only support OpenWRT+ath9k on it. I'm sure more than a few people fell into that trap. :) Adrian _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
