Re: [RFC 5/6] ath9k: enable DFS pulse detection

[Christian Lamparter <chunkeey@googlemail.com>]

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.

> For example: you may not want to do DFS on the AR5416 NICs because
> (as documented in the open hal and earlier ath9k bits) there isn't
> support for radar pulses on the ext channel. So even if you had a
> successful DFS algorithm for this NIC, you'd have to somehow tell
> the DFS machinery that HT40+DFS channels aren't supported but
> HT20+DFS channels are.
well, that's a pity. We do have seperated HT feature sets for each
band but they are not seperated by operation mode...

[ 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." ]

Regards,
	Chr