1config WIRELESS_EXT 2 bool 3 4config WEXT_CORE 5 def_bool y 6 depends on CFG80211_WEXT || WIRELESS_EXT 7 8config WEXT_PROC 9 def_bool y 10 depends on PROC_FS 11 depends on WEXT_CORE 12 13config WEXT_SPY 14 bool 15 16config WEXT_PRIV 17 bool 18 19config CFG80211 20 tristate "cfg80211 - wireless configuration API" 21 depends on RFKILL || !RFKILL 22 select FW_LOADER 23 ---help--- 24 cfg80211 is the Linux wireless LAN (802.11) configuration API. 25 Enable this if you have a wireless device. 26 27 For more information refer to documentation on the wireless wiki: 28 29 http://wireless.kernel.org/en/developers/Documentation/cfg80211 30 31 When built as a module it will be called cfg80211. 32 33config NL80211_TESTMODE 34 bool "nl80211 testmode command" 35 depends on CFG80211 36 help 37 The nl80211 testmode command helps implementing things like 38 factory calibration or validation tools for wireless chips. 39 40 Select this option ONLY for kernels that are specifically 41 built for such purposes. 42 43 Debugging tools that are supposed to end up in the hands of 44 users should better be implemented with debugfs. 45 46 Say N. 47 48config CFG80211_DEVELOPER_WARNINGS 49 bool "enable developer warnings" 50 depends on CFG80211 51 default n 52 help 53 This option enables some additional warnings that help 54 cfg80211 developers and driver developers, but beware that 55 they can also trigger due to races with userspace. 56 57 For example, when a driver reports that it was disconnected 58 from the AP, but the user disconnects manually at the same 59 time, the warning might trigger spuriously due to races. 60 61 Say Y only if you are developing cfg80211 or a driver based 62 on it (or mac80211). 63 64 65config CFG80211_CERTIFICATION_ONUS 66 bool "cfg80211 certification onus" 67 depends on CFG80211 && EXPERT 68 default n 69 ---help--- 70 You should disable this option unless you are both capable 71 and willing to ensure your system will remain regulatory 72 compliant with the features available under this option. 73 Some options may still be under heavy development and 74 for whatever reason regulatory compliance has not or 75 cannot yet be verified. Regulatory verification may at 76 times only be possible until you have the final system 77 in place. 78 79 This option should only be enabled by system integrators 80 or distributions that have done work necessary to ensure 81 regulatory certification on the system with the enabled 82 features. Alternatively you can enable this option if 83 you are a wireless researcher and are working in a controlled 84 and approved environment by your local regulatory agency. 85 86config CFG80211_REG_CELLULAR_HINTS 87 bool "cfg80211 regulatory support for cellular base station hints" 88 depends on CFG80211_CERTIFICATION_ONUS 89 ---help--- 90 This option enables support for parsing regulatory hints 91 from cellular base stations. If enabled and at least one driver 92 claims support for parsing cellular base station hints the 93 regulatory core will allow and parse these regulatory hints. 94 The regulatory core will only apply these regulatory hints on 95 drivers that support this feature. You should only enable this 96 feature if you have tested and validated this feature on your 97 systems. 98 99config CFG80211_REG_RELAX_NO_IR 100 bool "cfg80211 support for NO_IR relaxation" 101 depends on CFG80211_CERTIFICATION_ONUS 102 ---help--- 103 This option enables support for relaxation of the NO_IR flag for 104 situations that certain regulatory bodies have provided clarifications 105 on how relaxation can occur. This feature has an inherent dependency on 106 userspace features which must have been properly tested and as such is 107 not enabled by default. 108 109 A relaxation feature example is allowing the operation of a P2P group 110 owner (GO) on channels marked with NO_IR if there is an additional BSS 111 interface which associated to an AP which userspace assumes or confirms 112 to be an authorized master, i.e., with radar detection support and DFS 113 capabilities. However, note that in order to not create daisy chain 114 scenarios, this relaxation is not allowed in cases where the BSS client 115 is associated to P2P GO and in addition the P2P GO instantiated on 116 a channel due to this relaxation should not allow connection from 117 non P2P clients. 118 119 The regulatory core will apply these relaxations only for drivers that 120 support this feature by declaring the appropriate channel flags and 121 capabilities in their registration flow. 122 123config CFG80211_DEFAULT_PS 124 bool "enable powersave by default" 125 depends on CFG80211 126 default y 127 help 128 This option enables powersave mode by default. 129 130 If this causes your applications to misbehave you should fix your 131 applications instead -- they need to register their network 132 latency requirement, see Documentation/power/pm_qos_interface.txt. 133 134config CFG80211_DEBUGFS 135 bool "cfg80211 DebugFS entries" 136 depends on CFG80211 137 depends on DEBUG_FS 138 ---help--- 139 You can enable this if you want debugfs entries for cfg80211. 140 141 If unsure, say N. 142 143config CFG80211_INTERNAL_REGDB 144 bool "use statically compiled regulatory rules database" if EXPERT 145 default n 146 depends on CFG80211 147 ---help--- 148 This option generates an internal data structure representing 149 the wireless regulatory rules described in net/wireless/db.txt 150 and includes code to query that database. This is an alternative 151 to using CRDA for defining regulatory rules for the kernel. 152 153 Using this option requires some parsing of the db.txt at build time, 154 the parser will be upkept with the latest wireless-regdb updates but 155 older wireless-regdb formats will be ignored. The parser may later 156 be replaced to avoid issues with conflicts on versions of 157 wireless-regdb. 158 159 For details see: 160 161 http://wireless.kernel.org/en/developers/Regulatory 162 163 Most distributions have a CRDA package. So if unsure, say N. 164 165config CFG80211_CRDA_SUPPORT 166 bool "support CRDA" if CFG80211_INTERNAL_REGDB 167 default y 168 depends on CFG80211 169 help 170 You should enable this option unless you know for sure you have no 171 need for it, for example when using internal regdb (above) or the 172 database loaded as a firmware file. 173 174 If unsure, say Y. 175 176config CFG80211_WEXT 177 bool "cfg80211 wireless extensions compatibility" if !CFG80211_WEXT_EXPORT 178 depends on CFG80211 179 select WEXT_CORE 180 default y if CFG80211_WEXT_EXPORT 181 help 182 Enable this option if you need old userspace for wireless 183 extensions with cfg80211-based drivers. 184 185config CFG80211_WEXT_EXPORT 186 bool 187 depends on CFG80211 188 help 189 Drivers should select this option if they require cfg80211's 190 wext compatibility symbols to be exported. 191 192config LIB80211 193 tristate 194 default n 195 help 196 This options enables a library of common routines used 197 by IEEE802.11 wireless LAN drivers. 198 199 Drivers should select this themselves if needed. 200 201config LIB80211_CRYPT_WEP 202 tristate 203 204config LIB80211_CRYPT_CCMP 205 tristate 206 207config LIB80211_CRYPT_TKIP 208 tristate 209 210config LIB80211_DEBUG 211 bool "lib80211 debugging messages" 212 depends on LIB80211 213 default n 214 ---help--- 215 You can enable this if you want verbose debugging messages 216 from lib80211. 217 218 If unsure, say N. 219