Kconfig 6.6 KB

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