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