Kconfig 7.1 KB

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