1 # SPDX-License-Identifier: GPL-2.0-only <<
2 config WIRELESS_EXT 1 config WIRELESS_EXT
3 bool 2 bool
4 3
5 config WEXT_CORE 4 config WEXT_CORE
6 def_bool y 5 def_bool y
7 depends on CFG80211_WEXT || WIRELESS_E 6 depends on CFG80211_WEXT || WIRELESS_EXT
8 7
9 config WEXT_PROC 8 config WEXT_PROC
10 def_bool y 9 def_bool y
11 depends on PROC_FS 10 depends on PROC_FS
12 depends on WEXT_CORE 11 depends on WEXT_CORE
13 12
14 config WEXT_SPY 13 config WEXT_SPY
15 bool 14 bool
16 15
17 config WEXT_PRIV 16 config WEXT_PRIV
18 bool 17 bool
19 18
20 config CFG80211 19 config CFG80211
21 tristate "cfg80211 - wireless configur 20 tristate "cfg80211 - wireless configuration API"
22 depends on RFKILL || !RFKILL 21 depends on RFKILL || !RFKILL
23 select FW_LOADER !! 22 ---help---
24 select CRC32 <<
25 # may need to update this when certifi <<
26 # using a different algorithm, though <<
27 # (this is here rather than below to a <<
28 select CRYPTO_SHA256 if CFG80211_USE_K <<
29 help <<
30 cfg80211 is the Linux wireless LAN ( 23 cfg80211 is the Linux wireless LAN (802.11) configuration API.
31 Enable this if you have a wireless d 24 Enable this if you have a wireless device.
32 25
33 For more information refer to docume 26 For more information refer to documentation on the wireless wiki:
34 27
35 https://wireless.wiki.kernel.org/en/ !! 28 http://wireless.kernel.org/en/developers/Documentation/cfg80211
36 29
37 When built as a module it will be ca 30 When built as a module it will be called cfg80211.
38 31
39 if CFG80211 <<
40 <<
41 config NL80211_TESTMODE 32 config NL80211_TESTMODE
42 bool "nl80211 testmode command" 33 bool "nl80211 testmode command"
>> 34 depends on CFG80211
43 help 35 help
44 The nl80211 testmode command helps i 36 The nl80211 testmode command helps implementing things like
45 factory calibration or validation to 37 factory calibration or validation tools for wireless chips.
46 38
47 Select this option ONLY for kernels 39 Select this option ONLY for kernels that are specifically
48 built for such purposes. 40 built for such purposes.
49 41
50 Debugging tools that are supposed to 42 Debugging tools that are supposed to end up in the hands of
51 users should better be implemented w 43 users should better be implemented with debugfs.
52 44
53 Say N. 45 Say N.
54 46
55 config CFG80211_DEVELOPER_WARNINGS 47 config CFG80211_DEVELOPER_WARNINGS
56 bool "enable developer warnings" 48 bool "enable developer warnings"
>> 49 depends on CFG80211
57 default n 50 default n
58 help 51 help
59 This option enables some additional 52 This option enables some additional warnings that help
60 cfg80211 developers and driver devel !! 53 cfg80211 developers and driver developers, but that can
61 they can also trigger due to races w !! 54 trigger due to races with userspace.
62 55
63 For example, when a driver reports t 56 For example, when a driver reports that it was disconnected
64 from the AP, but the user disconnect 57 from the AP, but the user disconnects manually at the same
65 time, the warning might trigger spur 58 time, the warning might trigger spuriously due to races.
66 59
67 Say Y only if you are developing cfg 60 Say Y only if you are developing cfg80211 or a driver based
68 on it (or mac80211). 61 on it (or mac80211).
69 62
70 63
>> 64 config CFG80211_REG_DEBUG
>> 65 bool "cfg80211 regulatory debugging"
>> 66 depends on CFG80211
>> 67 default n
>> 68 ---help---
>> 69 You can enable this if you want to debug regulatory changes.
>> 70 For more information on cfg80211 regulatory refer to the wireless
>> 71 wiki:
>> 72
>> 73 http://wireless.kernel.org/en/developers/Regulatory
>> 74
>> 75 If unsure, say N.
>> 76
71 config CFG80211_CERTIFICATION_ONUS 77 config CFG80211_CERTIFICATION_ONUS
72 bool "cfg80211 certification onus" 78 bool "cfg80211 certification onus"
73 depends on EXPERT !! 79 depends on CFG80211 && EXPERT
74 default n 80 default n
75 help !! 81 ---help---
76 You should disable this option unles 82 You should disable this option unless you are both capable
77 and willing to ensure your system wi 83 and willing to ensure your system will remain regulatory
78 compliant with the features availabl 84 compliant with the features available under this option.
79 Some options may still be under heav 85 Some options may still be under heavy development and
80 for whatever reason regulatory compl 86 for whatever reason regulatory compliance has not or
81 cannot yet be verified. Regulatory v 87 cannot yet be verified. Regulatory verification may at
82 times only be possible until you hav 88 times only be possible until you have the final system
83 in place. 89 in place.
84 90
85 This option should only be enabled b 91 This option should only be enabled by system integrators
86 or distributions that have done work 92 or distributions that have done work necessary to ensure
87 regulatory certification on the syst 93 regulatory certification on the system with the enabled
88 features. Alternatively you can enab 94 features. Alternatively you can enable this option if
89 you are a wireless researcher and ar 95 you are a wireless researcher and are working in a controlled
90 and approved environment by your loc 96 and approved environment by your local regulatory agency.
91 97
92 config CFG80211_REQUIRE_SIGNED_REGDB <<
93 bool "require regdb signature" if CFG8 <<
94 default y <<
95 select SYSTEM_DATA_VERIFICATION <<
96 help <<
97 Require that in addition to the "reg <<
98 "regulatory.db.p7s" can be loaded wi <<
99 signature for the regulatory.db file <<
100 keys in the certs/ directory. <<
101 <<
102 config CFG80211_USE_KERNEL_REGDB_KEYS <<
103 bool "allow regdb keys shipped with th <<
104 default y <<
105 depends on CFG80211_REQUIRE_SIGNED_REG <<
106 help <<
107 Allow the regulatory database to be <<
108 which certificates are part of the k <<
109 (in net/wireless/certs/). <<
110 <<
111 This is currently only Seth Forshee' <<
112 database maintainer. <<
113 <<
114 config CFG80211_EXTRA_REGDB_KEYDIR <<
115 string "additional regdb key directory <<
116 depends on CFG80211_REQUIRE_SIGNED_REG <<
117 help <<
118 If selected, point to a directory wi <<
119 certificates like in the kernel sour <<
120 that shall be accepted for a signed <<
121 <<
122 Note that you need to also select th <<
123 for your certificates, and if cfg802 <<
124 <<
125 config CFG80211_REG_CELLULAR_HINTS <<
126 bool "cfg80211 regulatory support for <<
127 depends on CFG80211_CERTIFICATION_ONUS <<
128 help <<
129 This option enables support for pars <<
130 from cellular base stations. If enab <<
131 claims support for parsing cellular <<
132 regulatory core will allow and parse <<
133 The regulatory core will only apply <<
134 drivers that support this feature. Y <<
135 feature if you have tested and valid <<
136 systems. <<
137 <<
138 config CFG80211_REG_RELAX_NO_IR <<
139 bool "cfg80211 support for NO_IR relax <<
140 depends on CFG80211_CERTIFICATION_ONUS <<
141 help <<
142 This option enables support for relax <<
143 situations that certain regulatory bo <<
144 on how relaxation can occur. This fea <<
145 userspace features which must have be <<
146 not enabled by default. <<
147 <<
148 A relaxation feature example is allow <<
149 owner (GO) on channels marked with NO <<
150 interface which associated to an AP w <<
151 to be an authorized master, i.e., wit <<
152 capabilities. However, note that in o <<
153 scenarios, this relaxation is not all <<
154 is associated to P2P GO and in additi <<
155 a channel due to this relaxation shou <<
156 non P2P clients. <<
157 <<
158 The regulatory core will apply these <<
159 support this feature by declaring the <<
160 capabilities in their registration fl <<
161 <<
162 config CFG80211_DEFAULT_PS 98 config CFG80211_DEFAULT_PS
163 bool "enable powersave by default" 99 bool "enable powersave by default"
>> 100 depends on CFG80211
164 default y 101 default y
165 help 102 help
166 This option enables powersave mode b 103 This option enables powersave mode by default.
167 104
168 If this causes your applications to 105 If this causes your applications to misbehave you should fix your
169 applications instead -- they need to 106 applications instead -- they need to register their network
170 latency requirement, see Documentati !! 107 latency requirement, see Documentation/power/pm_qos_interface.txt.
171 108
172 config CFG80211_DEBUGFS 109 config CFG80211_DEBUGFS
173 bool "cfg80211 DebugFS entries" 110 bool "cfg80211 DebugFS entries"
>> 111 depends on CFG80211
174 depends on DEBUG_FS 112 depends on DEBUG_FS
175 help !! 113 ---help---
176 You can enable this if you want debu !! 114 You can enable this if you want to debugfs entries for cfg80211.
177 115
178 If unsure, say N. 116 If unsure, say N.
179 117
180 config CFG80211_CRDA_SUPPORT !! 118 config CFG80211_INTERNAL_REGDB
181 bool "support CRDA" if EXPERT !! 119 bool "use statically compiled regulatory rules database" if EXPERT
182 default y !! 120 default n
183 help !! 121 depends on CFG80211
184 You should enable this option unless !! 122 ---help---
185 need for it, for example when using !! 123 This option generates an internal data structure representing
186 a firmware file. !! 124 the wireless regulatory rules described in net/wireless/db.txt
>> 125 and includes code to query that database. This is an alternative
>> 126 to using CRDA for defining regulatory rules for the kernel.
>> 127
>> 128 For details see:
187 129
188 If unsure, say Y. !! 130 http://wireless.kernel.org/en/developers/Regulatory
>> 131
>> 132 Most distributions have a CRDA package. So if unsure, say N.
189 133
190 config CFG80211_WEXT 134 config CFG80211_WEXT
191 bool "cfg80211 wireless extensions com !! 135 bool "cfg80211 wireless extensions compatibility"
>> 136 depends on CFG80211
192 select WEXT_CORE 137 select WEXT_CORE
193 default y if CFG80211_WEXT_EXPORT <<
194 help 138 help
195 Enable this option if you need old u 139 Enable this option if you need old userspace for wireless
196 extensions with cfg80211-based drive 140 extensions with cfg80211-based drivers.
197 141
198 config CFG80211_WEXT_EXPORT <<
199 bool <<
200 help <<
201 Drivers should select this option if <<
202 wext compatibility symbols to be exp <<
203 <<
204 config CFG80211_KUNIT_TEST <<
205 tristate "KUnit tests for cfg80211" if <<
206 depends on KUNIT <<
207 depends on CFG80211 <<
208 default KUNIT_ALL_TESTS <<
209 help <<
210 Enable this option to test cfg80211 <<
211 <<
212 If unsure, say N. <<
213 <<
214 endif # CFG80211 <<
215 <<
216 config LIB80211 142 config LIB80211
217 tristate 143 tristate
218 default n 144 default n
219 help 145 help
220 This options enables a library of co 146 This options enables a library of common routines used
221 by IEEE802.11 wireless LAN drivers. 147 by IEEE802.11 wireless LAN drivers.
222 148
223 Drivers should select this themselve 149 Drivers should select this themselves if needed.
224 150
225 config LIB80211_CRYPT_WEP 151 config LIB80211_CRYPT_WEP
226 tristate 152 tristate
227 select CRYPTO_LIB_ARC4 <<
228 153
229 config LIB80211_CRYPT_CCMP 154 config LIB80211_CRYPT_CCMP
230 tristate 155 tristate
231 select CRYPTO <<
232 select CRYPTO_AES <<
233 select CRYPTO_CCM <<
234 156
235 config LIB80211_CRYPT_TKIP 157 config LIB80211_CRYPT_TKIP
236 tristate 158 tristate
237 select CRYPTO_LIB_ARC4 <<
238 159
239 config LIB80211_DEBUG 160 config LIB80211_DEBUG
240 bool "lib80211 debugging messages" 161 bool "lib80211 debugging messages"
241 depends on LIB80211 162 depends on LIB80211
242 default n 163 default n
243 help !! 164 ---help---
244 You can enable this if you want verb 165 You can enable this if you want verbose debugging messages
245 from lib80211. 166 from lib80211.
246 167
247 If unsure, say N. 168 If unsure, say N.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.