Kconfig 6.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. #
  3. # Intel Centrino wireless drivers
  4. #
  5. config IPW2100
  6. tristate "Intel PRO/Wireless 2100 Network Connection"
  7. depends on PCI && CFG80211
  8. select WIRELESS_EXT
  9. select WEXT_SPY
  10. select WEXT_PRIV
  11. select FW_LOADER
  12. select LIB80211
  13. select LIBIPW
  14. help
  15. A driver for the Intel PRO/Wireless 2100 Network
  16. Connection 802.11b wireless network adapter.
  17. See <file:Documentation/networking/device_drivers/wifi/intel/ipw2100.rst>
  18. for information on the capabilities currently enabled in this driver
  19. and for tips for debugging issues and problems.
  20. In order to use this driver, you will need a firmware image for it.
  21. You can obtain the firmware from
  22. <http://ipw2100.sf.net/>. Once you have the firmware image, you
  23. will need to place it in /lib/firmware.
  24. You will also very likely need the Wireless Tools in order to
  25. configure your card:
  26. <https://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
  27. It is recommended that you compile this driver as a module (M)
  28. rather than built-in (Y). This driver requires firmware at device
  29. initialization time, and when built-in this typically happens
  30. before the filesystem is accessible (hence firmware will be
  31. unavailable and initialization will fail). If you do choose to build
  32. this driver into your kernel image, you can avoid this problem by
  33. including the firmware and a firmware loader in an initramfs.
  34. config IPW2100_MONITOR
  35. bool "Enable promiscuous mode"
  36. depends on IPW2100
  37. help
  38. Enables promiscuous/monitor mode support for the ipw2100 driver.
  39. With this feature compiled into the driver, you can switch to
  40. promiscuous mode via the Wireless Tool's Monitor mode. While in this
  41. mode, no packets can be sent.
  42. config IPW2100_DEBUG
  43. bool "Enable full debugging output in IPW2100 module."
  44. depends on IPW2100
  45. help
  46. This option will enable debug tracing output for the IPW2100.
  47. This will result in the kernel module being ~60k larger. You can
  48. control which debug output is sent to the kernel log by setting the
  49. value in
  50. /sys/bus/pci/drivers/ipw2100/debug_level
  51. This entry will only exist if this option is enabled.
  52. If you are not trying to debug or develop the IPW2100 driver, you
  53. most likely want to say N here.
  54. config IPW2200
  55. tristate "Intel PRO/Wireless 2200BG and 2915ABG Network Connection"
  56. depends on PCI && CFG80211
  57. select CFG80211_WEXT_EXPORT
  58. select WIRELESS_EXT
  59. select WEXT_SPY
  60. select WEXT_PRIV
  61. select FW_LOADER
  62. select LIB80211
  63. select LIBIPW
  64. help
  65. A driver for the Intel PRO/Wireless 2200BG and 2915ABG Network
  66. Connection adapters.
  67. See <file:Documentation/networking/device_drivers/wifi/intel/ipw2200.rst>
  68. for information on the capabilities currently enabled in this
  69. driver and for tips for debugging issues and problems.
  70. In order to use this driver, you will need a firmware image for it.
  71. You can obtain the firmware from
  72. <http://ipw2200.sf.net/>. See the above referenced README.ipw2200
  73. for information on where to install the firmware images.
  74. You will also very likely need the Wireless Tools in order to
  75. configure your card:
  76. <https://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
  77. It is recommended that you compile this driver as a module (M)
  78. rather than built-in (Y). This driver requires firmware at device
  79. initialization time, and when built-in this typically happens
  80. before the filesystem is accessible (hence firmware will be
  81. unavailable and initialization will fail). If you do choose to build
  82. this driver into your kernel image, you can avoid this problem by
  83. including the firmware and a firmware loader in an initramfs.
  84. config IPW2200_MONITOR
  85. bool "Enable promiscuous mode"
  86. depends on IPW2200
  87. help
  88. Enables promiscuous/monitor mode support for the ipw2200 driver.
  89. With this feature compiled into the driver, you can switch to
  90. promiscuous mode via the Wireless Tool's Monitor mode. While in this
  91. mode, no packets can be sent.
  92. config IPW2200_RADIOTAP
  93. bool "Enable radiotap format 802.11 raw packet support"
  94. depends on IPW2200_MONITOR
  95. config IPW2200_PROMISCUOUS
  96. bool "Enable creation of a RF radiotap promiscuous interface"
  97. depends on IPW2200_MONITOR
  98. select IPW2200_RADIOTAP
  99. help
  100. Enables the creation of a second interface prefixed 'rtap'.
  101. This second interface will provide every received in radiotap
  102. format.
  103. This is useful for performing wireless network analysis while
  104. maintaining an active association.
  105. Example usage:
  106. % modprobe ipw2200 rtap_iface=1
  107. % ifconfig rtap0 up
  108. % tethereal -i rtap0
  109. If you do not specify 'rtap_iface=1' as a module parameter then
  110. the rtap interface will not be created and you will need to turn
  111. it on via sysfs:
  112. % echo 1 > /sys/bus/pci/drivers/ipw2200/*/rtap_iface
  113. config IPW2200_QOS
  114. bool "Enable QoS support"
  115. depends on IPW2200
  116. config IPW2200_DEBUG
  117. bool "Enable full debugging output in IPW2200 module."
  118. depends on IPW2200
  119. help
  120. This option will enable low level debug tracing output for IPW2200.
  121. Note, normal debug code is already compiled in. This low level
  122. debug option enables debug on hot paths (e.g Tx, Rx, ISR) and
  123. will result in the kernel module being ~70 larger. Most users
  124. will typically not need this high verbosity debug information.
  125. If you are not sure, say N here.
  126. config LIBIPW
  127. tristate
  128. depends on PCI && CFG80211
  129. select WIRELESS_EXT
  130. select WEXT_SPY
  131. select CRYPTO
  132. select CRYPTO_MICHAEL_MIC
  133. select CRC32
  134. select LIB80211
  135. select LIB80211_CRYPT_WEP
  136. select LIB80211_CRYPT_TKIP
  137. select LIB80211_CRYPT_CCMP
  138. help
  139. This option enables the hardware independent IEEE 802.11
  140. networking stack. This component is deprecated in favor of the
  141. mac80211 component.
  142. config LIBIPW_DEBUG
  143. bool "Full debugging output for the LIBIPW component"
  144. depends on LIBIPW
  145. help
  146. This option will enable debug tracing output for the
  147. libipw component.
  148. This will result in the kernel module being ~70k larger. You
  149. can control which debug output is sent to the kernel log by
  150. setting the value in
  151. /proc/net/ieee80211/debug_level
  152. For example:
  153. % echo 0x00000FFO > /proc/net/ieee80211/debug_level
  154. For a list of values you can assign to debug_level, you
  155. can look at the bit mask values in ieee80211.h
  156. If you are not trying to debug or develop the libipw
  157. component, you most likely want to say N here.