Kconfig 6.7 KB

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