summaryrefslogtreecommitdiff
path: root/security
diff options
context:
space:
mode:
authorBruno Randolf <br1@einfach.org>2010-12-08 13:59:24 +0900
committerJohn W. Linville <linville@tuxdriver.com>2010-12-13 15:23:27 -0500
commita7ffac9591a2a0ee74c431396ae475a8d0caa51e (patch)
tree174134b89e490592003307263e6b3964d9a1eacf /security
parenta08e7ade9ddf4fe79576f953cc5c1725e944d26c (diff)
downloadlinux-3.10-a7ffac9591a2a0ee74c431396ae475a8d0caa51e.tar.gz
linux-3.10-a7ffac9591a2a0ee74c431396ae475a8d0caa51e.tar.bz2
linux-3.10-a7ffac9591a2a0ee74c431396ae475a8d0caa51e.zip
cfg80211: Add antenna availability information
Add a field to wiphy for the hardware to report the availble antennas for configuration. Only if this is set to something bigger than zero, will the anntenna configuration ops be executed. Allthough this could be a simple number of antennas, I defined it as a bitmap of antennas which are available for configuration, since it's more consistent with the rest of the antenna API and there could be cases where the hardware allows only configuration of certain antennas. As it does not make much of a difference in size or normal usage, I think it's better to be able to support this, in case the need arises. The antenna configuration is now also checked against the availabe antennas and rejected if it does not match. Signed-off-by: Bruno Randolf <br1@einfach.org> -- v3: always apply available antenna mask (for "all" antennas case). v2: reject antenna configurations which don't match the available antennas Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions