2 # Intel Centrino wireless drivers
6 tristate "Intel PRO/Wireless 2100 Network Connection"
7 depends on PCI && WLAN_80211
13 A driver for the Intel PRO/Wireless 2100 Network
14 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.
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.
25 You will also very likely need the Wireless Tools in order to
28 <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
30 It is recommended that you compile this driver as a module (M)
31 rather than built-in (Y). This driver requires firmware at device
32 initialization time, and when built-in this typically happens
33 before the filesystem is accessible (hence firmware will be
34 unavailable and initialization will fail). If you do choose to build
35 this driver into your kernel image, you can avoid this problem by
36 including the firmware and a firmware loader in an initramfs.
38 config IPW2100_MONITOR
39 bool "Enable promiscuous mode"
42 Enables promiscuous/monitor mode support for the ipw2100 driver.
43 With this feature compiled into the driver, you can switch to
44 promiscuous mode via the Wireless Tool's Monitor mode. While in this
45 mode, no packets can be sent.
48 bool "Enable full debugging output in IPW2100 module."
51 This option will enable debug tracing output for the IPW2100.
53 This will result in the kernel module being ~60k larger. You can
54 control which debug output is sent to the kernel log by setting the
57 /sys/bus/pci/drivers/ipw2100/debug_level
59 This entry will only exist if this option is enabled.
61 If you are not trying to debug or develop the IPW2100 driver, you
62 most likely want to say N here.
65 tristate "Intel PRO/Wireless 2200BG and 2915ABG Network Connection"
66 depends on PCI && WLAN_80211
72 A driver for the Intel PRO/Wireless 2200BG and 2915ABG Network
75 See <file:Documentation/networking/README.ipw2200> for
76 information on the capabilities currently enabled in this
77 driver and for tips for debugging issues and problems.
79 In order to use this driver, you will need a firmware image for it.
80 You can obtain the firmware from
81 <http://ipw2200.sf.net/>. See the above referenced README.ipw2200
82 for information on where to install the firmware images.
84 You will also very likely need the Wireless Tools in order to
87 <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
89 It is recommended that you compile this driver as a module (M)
90 rather than built-in (Y). This driver requires firmware at device
91 initialization time, and when built-in this typically happens
92 before the filesystem is accessible (hence firmware will be
93 unavailable and initialization will fail). If you do choose to build
94 this driver into your kernel image, you can avoid this problem by
95 including the firmware and a firmware loader in an initramfs.
97 config IPW2200_MONITOR
98 bool "Enable promiscuous mode"
101 Enables promiscuous/monitor mode support for the ipw2200 driver.
102 With this feature compiled into the driver, you can switch to
103 promiscuous mode via the Wireless Tool's Monitor mode. While in this
104 mode, no packets can be sent.
106 config IPW2200_RADIOTAP
107 bool "Enable radiotap format 802.11 raw packet support"
108 depends on IPW2200_MONITOR
110 config IPW2200_PROMISCUOUS
111 bool "Enable creation of a RF radiotap promiscuous interface"
112 depends on IPW2200_MONITOR
113 select IPW2200_RADIOTAP
115 Enables the creation of a second interface prefixed 'rtap'.
116 This second interface will provide every received in radiotap
119 This is useful for performing wireless network analysis while
120 maintaining an active association.
124 % modprobe ipw2200 rtap_iface=1
128 If you do not specify 'rtap_iface=1' as a module parameter then
129 the rtap interface will not be created and you will need to turn
132 % echo 1 > /sys/bus/pci/drivers/ipw2200/*/rtap_iface
135 bool "Enable QoS support"
136 depends on IPW2200 && EXPERIMENTAL
139 bool "Enable full debugging output in IPW2200 module."
142 This option will enable low level debug tracing output for IPW2200.
144 Note, normal debug code is already compiled in. This low level
145 debug option enables debug on hot paths (e.g Tx, Rx, ISR) and
146 will result in the kernel module being ~70 larger. Most users
147 will typically not need this high verbosity debug information.
149 If you are not sure, say N here.
158 select CRYPTO_MICHAEL_MIC
162 select LIB80211_CRYPT_WEP
163 select LIB80211_CRYPT_TKIP
164 select LIB80211_CRYPT_CCMP
166 This option enables the hardware independent IEEE 802.11
167 networking stack. This component is deprecated in favor of the
171 bool "Full debugging output for the LIBIPW component"
174 This option will enable debug tracing output for the
177 This will result in the kernel module being ~70k larger. You
178 can control which debug output is sent to the kernel log by
181 /proc/net/ieee80211/debug_level
185 % echo 0x00000FFO > /proc/net/ieee80211/debug_level
187 For a list of values you can assign to debug_level, you
188 can look at the bit mask values in <net/ieee80211.h>
190 If you are not trying to debug or develop the libipw
191 component, you most likely want to say N here.