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