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