6 depends on CFG80211_WEXT || WIRELESS_EXT
20 tristate "cfg80211 - wireless configuration API"
21 depends on RFKILL || !RFKILL
23 cfg80211 is the Linux wireless LAN (802.11) configuration API.
24 Enable this if you have a wireless device.
26 For more information refer to documentation on the wireless wiki:
28 http://wireless.kernel.org/en/developers/Documentation/cfg80211
30 When built as a module it will be called cfg80211.
32 config NL80211_TESTMODE
33 bool "nl80211 testmode command"
36 The nl80211 testmode command helps implementing things like
37 factory calibration or validation tools for wireless chips.
39 Select this option ONLY for kernels that are specifically
40 built for such purposes.
42 Debugging tools that are supposed to end up in the hands of
43 users should better be implemented with debugfs.
47 config CFG80211_DEVELOPER_WARNINGS
48 bool "enable developer warnings"
52 This option enables some additional warnings that help
53 cfg80211 developers and driver developers, but that can
54 trigger due to races with userspace.
56 For example, when a driver reports that it was disconnected
57 from the AP, but the user disconnects manually at the same
58 time, the warning might trigger spuriously due to races.
60 Say Y only if you are developing cfg80211 or a driver based
64 config CFG80211_REG_DEBUG
65 bool "cfg80211 regulatory debugging"
69 You can enable this if you want to debug regulatory changes.
70 For more information on cfg80211 regulatory refer to the wireless
73 http://wireless.kernel.org/en/developers/Regulatory
77 config CFG80211_CERTIFICATION_ONUS
78 bool "cfg80211 certification onus"
79 depends on CFG80211 && EXPERT
82 You should disable this option unless you are both capable
83 and willing to ensure your system will remain regulatory
84 compliant with the features available under this option.
85 Some options may still be under heavy development and
86 for whatever reason regulatory compliance has not or
87 cannot yet be verified. Regulatory verification may at
88 times only be possible until you have the final system
91 This option should only be enabled by system integrators
92 or distributions that have done work necessary to ensure
93 regulatory certification on the system with the enabled
94 features. Alternatively you can enable this option if
95 you are a wireless researcher and are working in a controlled
96 and approved environment by your local regulatory agency.
98 config CFG80211_REG_CELLULAR_HINTS
99 bool "cfg80211 regulatory support for cellular base station hints"
100 depends on CFG80211_CERTIFICATION_ONUS
102 This option enables support for parsing regulatory hints
103 from cellular base stations. If enabled and at least one driver
104 claims support for parsing cellular base station hints the
105 regulatory core will allow and parse these regulatory hints.
106 The regulatory core will only apply these regulatory hints on
107 drivers that support this feature. You should only enable this
108 feature if you have tested and validated this feature on your
111 config CFG80211_REG_RELAX_NO_IR
112 bool "cfg80211 support for NO_IR relaxation"
113 depends on CFG80211_CERTIFICATION_ONUS
115 This option enables support for relaxation of the NO_IR flag for
116 situations that certain regulatory bodies have provided clarifications
117 on how relaxation can occur. This feature has an inherent dependency on
118 userspace features which must have been properly tested and as such is
119 not enabled by default.
121 A relaxation feature example is allowing the operation of a P2P group
122 owner (GO) on channels marked with NO_IR if there is an additional BSS
123 interface which associated to an AP which userspace assumes or confirms
124 to be an authorized master, i.e., with radar detection support and DFS
125 capabilities. However, note that in order to not create daisy chain
126 scenarios, this relaxation is not allowed in cases that the BSS client
127 is associated to P2P GO and in addition the P2P GO instantiated on
128 a channel due to this relaxation should not allow connection from
131 The regulatory core will apply these relaxations only for drivers that
132 support this feature by declaring the appropriate channel flags and
133 capabilities in their registration flow.
135 config CFG80211_DEFAULT_PS
136 bool "enable powersave by default"
140 This option enables powersave mode by default.
142 If this causes your applications to misbehave you should fix your
143 applications instead -- they need to register their network
144 latency requirement, see Documentation/power/pm_qos_interface.txt.
146 config CFG80211_DEBUGFS
147 bool "cfg80211 DebugFS entries"
151 You can enable this if you want to debugfs entries for cfg80211.
155 config CFG80211_INTERNAL_REGDB
156 bool "use statically compiled regulatory rules database" if EXPERT
160 This option generates an internal data structure representing
161 the wireless regulatory rules described in net/wireless/db.txt
162 and includes code to query that database. This is an alternative
163 to using CRDA for defining regulatory rules for the kernel.
165 Using this option requires some parsing of the db.txt at build time,
166 the parser will be upkept with the latest wireless-regdb updates but
167 older wireless-regdb formats will be ignored. The parser may later
168 be replaced to avoid issues with conflicts on versions of
173 http://wireless.kernel.org/en/developers/Regulatory
175 Most distributions have a CRDA package. So if unsure, say N.
178 bool "cfg80211 wireless extensions compatibility" if !CFG80211_WEXT_EXPORT
181 default y if CFG80211_WEXT_EXPORT
183 Enable this option if you need old userspace for wireless
184 extensions with cfg80211-based drivers.
186 config CFG80211_WEXT_EXPORT
190 Drivers should select this option if they require cfg80211's
191 wext compatibility symbols to be exported.
197 This options enables a library of common routines used
198 by IEEE802.11 wireless LAN drivers.
200 Drivers should select this themselves if needed.
202 config LIB80211_CRYPT_WEP
205 config LIB80211_CRYPT_CCMP
208 config LIB80211_CRYPT_TKIP
211 config LIB80211_DEBUG
212 bool "lib80211 debugging messages"
216 You can enable this if you want verbose debugging messages