aboutsummaryrefslogtreecommitdiffstats
path: root/package/utils
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2014-05-03 21:14:56 +0000
committerFelix Fietkau <nbd@openwrt.org>2014-05-03 21:14:56 +0000
commitc9b99da7a5e4cb9d63d841a6e282ce59df6df57c (patch)
treec7a0e35ce639017caa4f8a542edc3e11f6393c21 /package/utils
parent6c5f0f0caa85885aea6c1ada00ca186a437ee5c1 (diff)
downloadupstream-c9b99da7a5e4cb9d63d841a6e282ce59df6df57c.tar.gz
upstream-c9b99da7a5e4cb9d63d841a6e282ce59df6df57c.tar.bz2
upstream-c9b99da7a5e4cb9d63d841a6e282ce59df6df57c.zip
ath: Add config option for DFS support
This patch adds a config option to enable DFS in ath9k and ath10k drivers (with ath10k you need the AP-branch firmware). I'm not entirely sure about the regulatory compliance issues, though. As far as I understand, enabling the DFS_CERTIFIED config options implies that the device is certified for DFS. No doubt the original firmware has obtained such a certification, but not with the open source drivers. I suppose that as long as this is disabled in default builds (like ATH_USER_REGD) everything should be fine, but it would be nice to have out-of-the-box OpenWrt support for DFS. I'm also not sure whether the description of the configuration option should say something about regulatory compliance. Signed-off-by: Matti Laakso <malaakso@elisanet.fi> Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 40692
Diffstat (limited to 'package/utils')
0 files changed, 0 insertions, 0 deletions