Commit | Line | Data |
---|---|---|
0795cd29 JL |
1 | # |
2 | # Intel Centrino wireless drivers | |
3 | # | |
4 | ||
5 | config IPW2100 | |
6 | tristate "Intel PRO/Wireless 2100 Network Connection" | |
3107edba | 7 | depends on PCI && WLAN_80211 && CFG80211 |
0795cd29 JL |
8 | select WIRELESS_EXT |
9 | select FW_LOADER | |
10 | select LIB80211 | |
beb2a7f3 | 11 | select LIBIPW |
0795cd29 JL |
12 | ---help--- |
13 | A driver for the Intel PRO/Wireless 2100 Network | |
14 | Connection 802.11b wireless network adapter. | |
15 | ||
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 | ||
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 | ||
25 | You will also very likely need the Wireless Tools in order to | |
26 | configure your card: | |
27 | ||
28 | <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>. | |
29 | ||
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. | |
37 | ||
38 | config IPW2100_MONITOR | |
39 | bool "Enable promiscuous mode" | |
40 | depends on IPW2100 | |
41 | ---help--- | |
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. | |
46 | ||
47 | config IPW2100_DEBUG | |
48 | bool "Enable full debugging output in IPW2100 module." | |
49 | depends on IPW2100 | |
50 | ---help--- | |
51 | This option will enable debug tracing output for the IPW2100. | |
52 | ||
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 | |
55 | value in | |
56 | ||
57 | /sys/bus/pci/drivers/ipw2100/debug_level | |
58 | ||
59 | This entry will only exist if this option is enabled. | |
60 | ||
61 | If you are not trying to debug or develop the IPW2100 driver, you | |
62 | most likely want to say N here. | |
63 | ||
64 | config IPW2200 | |
65 | tristate "Intel PRO/Wireless 2200BG and 2915ABG Network Connection" | |
3107edba | 66 | depends on PCI && WLAN_80211 && CFG80211 |
0795cd29 JL |
67 | select WIRELESS_EXT |
68 | select FW_LOADER | |
69 | select LIB80211 | |
beb2a7f3 | 70 | select LIBIPW |
0795cd29 JL |
71 | ---help--- |
72 | A driver for the Intel PRO/Wireless 2200BG and 2915ABG Network | |
73 | Connection adapters. | |
74 | ||
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. | |
78 | ||
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. | |
83 | ||
84 | You will also very likely need the Wireless Tools in order to | |
85 | configure your card: | |
86 | ||
87 | <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>. | |
88 | ||
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. | |
96 | ||
97 | config IPW2200_MONITOR | |
98 | bool "Enable promiscuous mode" | |
99 | depends on IPW2200 | |
100 | ---help--- | |
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. | |
105 | ||
106 | config IPW2200_RADIOTAP | |
107 | bool "Enable radiotap format 802.11 raw packet support" | |
108 | depends on IPW2200_MONITOR | |
109 | ||
110 | config IPW2200_PROMISCUOUS | |
111 | bool "Enable creation of a RF radiotap promiscuous interface" | |
112 | depends on IPW2200_MONITOR | |
113 | select IPW2200_RADIOTAP | |
114 | ---help--- | |
115 | Enables the creation of a second interface prefixed 'rtap'. | |
116 | This second interface will provide every received in radiotap | |
117 | format. | |
118 | ||
119 | This is useful for performing wireless network analysis while | |
120 | maintaining an active association. | |
121 | ||
122 | Example usage: | |
123 | ||
124 | % modprobe ipw2200 rtap_iface=1 | |
125 | % ifconfig rtap0 up | |
126 | % tethereal -i rtap0 | |
127 | ||
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 | |
130 | it on via sysfs: | |
131 | ||
132 | % echo 1 > /sys/bus/pci/drivers/ipw2200/*/rtap_iface | |
133 | ||
134 | config IPW2200_QOS | |
135 | bool "Enable QoS support" | |
136 | depends on IPW2200 && EXPERIMENTAL | |
137 | ||
138 | config IPW2200_DEBUG | |
139 | bool "Enable full debugging output in IPW2200 module." | |
140 | depends on IPW2200 | |
141 | ---help--- | |
142 | This option will enable low level debug tracing output for IPW2200. | |
143 | ||
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. | |
148 | ||
149 | If you are not sure, say N here. | |
150 | ||
beb2a7f3 JL |
151 | config LIBIPW |
152 | tristate | |
3107edba | 153 | depends on PCI && WLAN_80211 && CFG80211 |
beb2a7f3 JL |
154 | select WIRELESS_EXT |
155 | select CRYPTO | |
156 | select CRYPTO_ARC4 | |
157 | select CRYPTO_ECB | |
158 | select CRYPTO_AES | |
159 | select CRYPTO_MICHAEL_MIC | |
160 | select CRYPTO_ECB | |
161 | select CRC32 | |
162 | select LIB80211 | |
163 | select LIB80211_CRYPT_WEP | |
164 | select LIB80211_CRYPT_TKIP | |
165 | select LIB80211_CRYPT_CCMP | |
166 | ---help--- | |
167 | This option enables the hardware independent IEEE 802.11 | |
168 | networking stack. This component is deprecated in favor of the | |
169 | mac80211 component. | |
170 | ||
171 | config LIBIPW_DEBUG | |
172 | bool "Full debugging output for the LIBIPW component" | |
173 | depends on LIBIPW | |
174 | ---help--- | |
175 | This option will enable debug tracing output for the | |
176 | libipw component. | |
177 | ||
178 | This will result in the kernel module being ~70k larger. You | |
179 | can control which debug output is sent to the kernel log by | |
180 | setting the value in | |
181 | ||
182 | /proc/net/ieee80211/debug_level | |
183 | ||
184 | For example: | |
185 | ||
186 | % echo 0x00000FFO > /proc/net/ieee80211/debug_level | |
187 | ||
188 | For a list of values you can assign to debug_level, you | |
f3734ee6 | 189 | can look at the bit mask values in ieee80211.h |
beb2a7f3 JL |
190 | |
191 | If you are not trying to debug or develop the libipw | |
192 | component, you most likely want to say N here. |