| .. | .. |
|---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
|---|
| 1 | 2 | config WIRELESS_EXT |
|---|
| 2 | 3 | bool |
|---|
| 3 | 4 | |
|---|
| .. | .. |
|---|
| 20 | 21 | tristate "cfg80211 - wireless configuration API" |
|---|
| 21 | 22 | depends on RFKILL || !RFKILL |
|---|
| 22 | 23 | select FW_LOADER |
|---|
| 24 | + select CRC32 |
|---|
| 23 | 25 | # may need to update this when certificates are changed and are |
|---|
| 24 | 26 | # using a different algorithm, though right now they shouldn't |
|---|
| 25 | 27 | # (this is here rather than below to allow it to be a module) |
|---|
| 26 | 28 | select CRYPTO_SHA256 if CFG80211_USE_KERNEL_REGDB_KEYS |
|---|
| 27 | | - ---help--- |
|---|
| 29 | + help |
|---|
| 28 | 30 | cfg80211 is the Linux wireless LAN (802.11) configuration API. |
|---|
| 29 | 31 | Enable this if you have a wireless device. |
|---|
| 30 | 32 | |
|---|
| 31 | 33 | For more information refer to documentation on the wireless wiki: |
|---|
| 32 | 34 | |
|---|
| 33 | | - http://wireless.kernel.org/en/developers/Documentation/cfg80211 |
|---|
| 35 | + https://wireless.wiki.kernel.org/en/developers/Documentation/cfg80211 |
|---|
| 34 | 36 | |
|---|
| 35 | 37 | When built as a module it will be called cfg80211. |
|---|
| 36 | 38 | |
|---|
| .. | .. |
|---|
| 70 | 72 | bool "cfg80211 certification onus" |
|---|
| 71 | 73 | depends on EXPERT |
|---|
| 72 | 74 | default n |
|---|
| 73 | | - ---help--- |
|---|
| 75 | + help |
|---|
| 74 | 76 | You should disable this option unless you are both capable |
|---|
| 75 | 77 | and willing to ensure your system will remain regulatory |
|---|
| 76 | 78 | compliant with the features available under this option. |
|---|
| .. | .. |
|---|
| 89 | 91 | |
|---|
| 90 | 92 | config CFG80211_REQUIRE_SIGNED_REGDB |
|---|
| 91 | 93 | bool "require regdb signature" if CFG80211_CERTIFICATION_ONUS |
|---|
| 92 | | - default y |
|---|
| 94 | + default y if !ROCKCHIP_THUNDER_BOOT |
|---|
| 93 | 95 | select SYSTEM_DATA_VERIFICATION |
|---|
| 94 | 96 | help |
|---|
| 95 | 97 | Require that in addition to the "regulatory.db" file a |
|---|
| .. | .. |
|---|
| 99 | 101 | |
|---|
| 100 | 102 | config CFG80211_USE_KERNEL_REGDB_KEYS |
|---|
| 101 | 103 | bool "allow regdb keys shipped with the kernel" if CFG80211_CERTIFICATION_ONUS |
|---|
| 102 | | - default y |
|---|
| 104 | + default y if !ROCKCHIP_THUNDER_BOOT |
|---|
| 103 | 105 | depends on CFG80211_REQUIRE_SIGNED_REGDB |
|---|
| 104 | 106 | help |
|---|
| 105 | 107 | Allow the regulatory database to be signed by one of the keys for |
|---|
| .. | .. |
|---|
| 123 | 125 | config CFG80211_REG_CELLULAR_HINTS |
|---|
| 124 | 126 | bool "cfg80211 regulatory support for cellular base station hints" |
|---|
| 125 | 127 | depends on CFG80211_CERTIFICATION_ONUS |
|---|
| 126 | | - ---help--- |
|---|
| 128 | + help |
|---|
| 127 | 129 | This option enables support for parsing regulatory hints |
|---|
| 128 | 130 | from cellular base stations. If enabled and at least one driver |
|---|
| 129 | 131 | claims support for parsing cellular base station hints the |
|---|
| .. | .. |
|---|
| 136 | 138 | config CFG80211_REG_RELAX_NO_IR |
|---|
| 137 | 139 | bool "cfg80211 support for NO_IR relaxation" |
|---|
| 138 | 140 | depends on CFG80211_CERTIFICATION_ONUS |
|---|
| 139 | | - ---help--- |
|---|
| 141 | + help |
|---|
| 140 | 142 | This option enables support for relaxation of the NO_IR flag for |
|---|
| 141 | 143 | situations that certain regulatory bodies have provided clarifications |
|---|
| 142 | 144 | on how relaxation can occur. This feature has an inherent dependency on |
|---|
| .. | .. |
|---|
| 165 | 167 | |
|---|
| 166 | 168 | If this causes your applications to misbehave you should fix your |
|---|
| 167 | 169 | applications instead -- they need to register their network |
|---|
| 168 | | - latency requirement, see Documentation/power/pm_qos_interface.txt. |
|---|
| 170 | + latency requirement, see Documentation/power/pm_qos_interface.rst. |
|---|
| 169 | 171 | |
|---|
| 170 | 172 | config CFG80211_DEBUGFS |
|---|
| 171 | 173 | bool "cfg80211 DebugFS entries" |
|---|
| 172 | 174 | depends on DEBUG_FS |
|---|
| 173 | | - ---help--- |
|---|
| 175 | + help |
|---|
| 174 | 176 | You can enable this if you want debugfs entries for cfg80211. |
|---|
| 175 | 177 | |
|---|
| 176 | 178 | If unsure, say N. |
|---|
| .. | .. |
|---|
| 180 | 182 | default y |
|---|
| 181 | 183 | help |
|---|
| 182 | 184 | 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 | + need for it, for example when using the regulatory database loaded as |
|---|
| 186 | + a firmware file. |
|---|
| 185 | 187 | |
|---|
| 186 | 188 | If unsure, say Y. |
|---|
| 187 | 189 | |
|---|
| .. | .. |
|---|
| 212 | 214 | |
|---|
| 213 | 215 | config LIB80211_CRYPT_WEP |
|---|
| 214 | 216 | tristate |
|---|
| 217 | + select CRYPTO_LIB_ARC4 |
|---|
| 215 | 218 | |
|---|
| 216 | 219 | config LIB80211_CRYPT_CCMP |
|---|
| 217 | 220 | tristate |
|---|
| 221 | + select CRYPTO |
|---|
| 222 | + select CRYPTO_AES |
|---|
| 223 | + select CRYPTO_CCM |
|---|
| 218 | 224 | |
|---|
| 219 | 225 | config LIB80211_CRYPT_TKIP |
|---|
| 220 | 226 | tristate |
|---|
| 227 | + select CRYPTO_LIB_ARC4 |
|---|
| 221 | 228 | |
|---|
| 222 | 229 | config LIB80211_DEBUG |
|---|
| 223 | 230 | bool "lib80211 debugging messages" |
|---|
| 224 | 231 | depends on LIB80211 |
|---|
| 225 | 232 | default n |
|---|
| 226 | | - ---help--- |
|---|
| 233 | + help |
|---|
| 227 | 234 | You can enable this if you want verbose debugging messages |
|---|
| 228 | 235 | from lib80211. |
|---|
| 229 | 236 | |
|---|