Lines Matching +full:on +full:- +full:the +full:- +full:go

1 # SPDX-License-Identifier: GPL-2.0-only
7 	depends on CFG80211_WEXT || WIRELESS_EXT
11 	depends on PROC_FS
12 	depends on WEXT_CORE
21 	tristate "cfg80211 - wireless configuration API"
22 	depends on RFKILL || !RFKILL
30 	  cfg80211 is the Linux wireless LAN (802.11) configuration API.
33 	  For more information refer to documentation on the wireless wiki:
44 	  The nl80211 testmode command helps implementing things like
50 	  Debugging tools that are supposed to end up in the hands of
64 	  from the AP, but the user disconnects manually at the same
65 	  time, the warning might trigger spuriously due to races.
68 	  on it (or mac80211).
73 	depends on EXPERT
78 	  compliant with the features available under this option.
82 	  times only be possible until you have the final system
87 	  regulatory certification on the system with the enabled
97 	  Require that in addition to the "regulatory.db" file a
99 	  signature for the regulatory.db file made by one of the
100 	  keys in the certs/ directory.
103 	bool "allow regdb keys shipped with the kernel" if CFG80211_CERTIFICATION_ONUS
105 	depends on CFG80211_REQUIRE_SIGNED_REGDB
107 	  Allow the regulatory database to be signed by one of the keys for
108 	  which certificates are part of the kernel sources
111 	  This is currently only Seth Forshee's key, who is the regulatory
116 	depends on CFG80211_REQUIRE_SIGNED_REGDB
118 	  If selected, point to a directory with DER-encoded X.509
119 	  certificates like in the kernel sources (net/wireless/certs/)
122 	  Note that you need to also select the correct CRYPTO_<hash> modules
123 	  for your certificates, and if cfg80211 is built-in they also must be.
127 	depends on CFG80211_CERTIFICATION_ONUS
131 	  claims support for parsing cellular base station hints the
133 	  The regulatory core will only apply these regulatory hints on
135 	  feature if you have tested and validated this feature on your
140 	depends on CFG80211_CERTIFICATION_ONUS
142 	 This option enables support for relaxation of the NO_IR flag for
144 	 on how relaxation can occur. This feature has an inherent dependency on
148 	 A relaxation feature example is allowing the operation of a P2P group
149 	 owner (GO) on channels marked with NO_IR if there is an additional BSS
153 	 scenarios, this relaxation is not allowed in cases where the BSS client
154 	 is associated to P2P GO and in addition the P2P GO instantiated on
158 	 The regulatory core will apply these relaxations only for drivers that
159 	 support this feature by declaring the appropriate channel flags and
169 	  applications instead -- they need to register their network
174 	depends on DEBUG_FS
185 	  need for it, for example when using the regulatory database loaded as
196 	  extensions with cfg80211-based drivers.
206 	depends on KUNIT
207 	depends on CFG80211
241 	depends on LIB80211