1ec8f24b7SThomas Gleixner# SPDX-License-Identifier: GPL-2.0-only 2367a1092SKalle Valo# 3367a1092SKalle Valo# Intel Centrino wireless drivers 4367a1092SKalle Valo# 5367a1092SKalle Valo 6367a1092SKalle Valoconfig IPW2100 7367a1092SKalle Valo tristate "Intel PRO/Wireless 2100 Network Connection" 8367a1092SKalle Valo depends on PCI && CFG80211 9367a1092SKalle Valo select WIRELESS_EXT 10367a1092SKalle Valo select WEXT_PRIV 11367a1092SKalle Valo select FW_LOADER 12367a1092SKalle Valo select LIBIPW 13a7f7f624SMasahiro Yamada help 14367a1092SKalle Valo A driver for the Intel PRO/Wireless 2100 Network 15367a1092SKalle Valo Connection 802.11b wireless network adapter. 16367a1092SKalle Valo 17132db935SJakub Kicinski See <file:Documentation/networking/device_drivers/wifi/intel/ipw2100.rst> 18b255e500SJakub Kicinski for information on the capabilities currently enabled in this driver 19b255e500SJakub Kicinski and for tips for debugging issues and problems. 20367a1092SKalle Valo 21367a1092SKalle Valo In order to use this driver, you will need a firmware image for it. 22367a1092SKalle Valo You can obtain the firmware from 23367a1092SKalle Valo <http://ipw2100.sf.net/>. Once you have the firmware image, you 24367a1092SKalle Valo will need to place it in /lib/firmware. 25367a1092SKalle Valo 26367a1092SKalle Valo You will also very likely need the Wireless Tools in order to 27367a1092SKalle Valo configure your card: 28367a1092SKalle Valo 29348cb5dcSAlexander A. Klimov <https://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>. 30367a1092SKalle Valo 31367a1092SKalle Valo It is recommended that you compile this driver as a module (M) 32367a1092SKalle Valo rather than built-in (Y). This driver requires firmware at device 33367a1092SKalle Valo initialization time, and when built-in this typically happens 34367a1092SKalle Valo before the filesystem is accessible (hence firmware will be 35367a1092SKalle Valo unavailable and initialization will fail). If you do choose to build 36367a1092SKalle Valo this driver into your kernel image, you can avoid this problem by 37367a1092SKalle Valo including the firmware and a firmware loader in an initramfs. 38367a1092SKalle Valo 39367a1092SKalle Valoconfig IPW2100_MONITOR 40367a1092SKalle Valo bool "Enable promiscuous mode" 41367a1092SKalle Valo depends on IPW2100 42a7f7f624SMasahiro Yamada help 43367a1092SKalle Valo Enables promiscuous/monitor mode support for the ipw2100 driver. 44367a1092SKalle Valo With this feature compiled into the driver, you can switch to 45367a1092SKalle Valo promiscuous mode via the Wireless Tool's Monitor mode. While in this 46367a1092SKalle Valo mode, no packets can be sent. 47367a1092SKalle Valo 48367a1092SKalle Valoconfig IPW2100_DEBUG 49367a1092SKalle Valo bool "Enable full debugging output in IPW2100 module." 50367a1092SKalle Valo depends on IPW2100 51a7f7f624SMasahiro Yamada help 52367a1092SKalle Valo This option will enable debug tracing output for the IPW2100. 53367a1092SKalle Valo 54367a1092SKalle Valo This will result in the kernel module being ~60k larger. You can 55367a1092SKalle Valo control which debug output is sent to the kernel log by setting the 56367a1092SKalle Valo value in 57367a1092SKalle Valo 58367a1092SKalle Valo /sys/bus/pci/drivers/ipw2100/debug_level 59367a1092SKalle Valo 60367a1092SKalle Valo This entry will only exist if this option is enabled. 61367a1092SKalle Valo 62367a1092SKalle Valo If you are not trying to debug or develop the IPW2100 driver, you 63367a1092SKalle Valo most likely want to say N here. 64367a1092SKalle Valo 65367a1092SKalle Valoconfig IPW2200 66367a1092SKalle Valo tristate "Intel PRO/Wireless 2200BG and 2915ABG Network Connection" 67367a1092SKalle Valo depends on PCI && CFG80211 68367a1092SKalle Valo select WIRELESS_EXT 69367a1092SKalle Valo select WEXT_PRIV 70367a1092SKalle Valo select FW_LOADER 71367a1092SKalle Valo select LIBIPW 72a7f7f624SMasahiro Yamada help 73367a1092SKalle Valo A driver for the Intel PRO/Wireless 2200BG and 2915ABG Network 74367a1092SKalle Valo Connection adapters. 75367a1092SKalle Valo 76132db935SJakub Kicinski See <file:Documentation/networking/device_drivers/wifi/intel/ipw2200.rst> 77b255e500SJakub Kicinski for information on the capabilities currently enabled in this 78367a1092SKalle Valo driver and for tips for debugging issues and problems. 79367a1092SKalle Valo 80367a1092SKalle Valo In order to use this driver, you will need a firmware image for it. 81367a1092SKalle Valo You can obtain the firmware from 82367a1092SKalle Valo <http://ipw2200.sf.net/>. See the above referenced README.ipw2200 83367a1092SKalle Valo for information on where to install the firmware images. 84367a1092SKalle Valo 85367a1092SKalle Valo You will also very likely need the Wireless Tools in order to 86367a1092SKalle Valo configure your card: 87367a1092SKalle Valo 88348cb5dcSAlexander A. Klimov <https://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>. 89367a1092SKalle Valo 90367a1092SKalle Valo It is recommended that you compile this driver as a module (M) 91367a1092SKalle Valo rather than built-in (Y). This driver requires firmware at device 92367a1092SKalle Valo initialization time, and when built-in this typically happens 93367a1092SKalle Valo before the filesystem is accessible (hence firmware will be 94367a1092SKalle Valo unavailable and initialization will fail). If you do choose to build 95367a1092SKalle Valo this driver into your kernel image, you can avoid this problem by 96367a1092SKalle Valo including the firmware and a firmware loader in an initramfs. 97367a1092SKalle Valo 98367a1092SKalle Valoconfig IPW2200_MONITOR 99367a1092SKalle Valo bool "Enable promiscuous mode" 100367a1092SKalle Valo depends on IPW2200 101a7f7f624SMasahiro Yamada help 102367a1092SKalle Valo Enables promiscuous/monitor mode support for the ipw2200 driver. 103367a1092SKalle Valo With this feature compiled into the driver, you can switch to 104367a1092SKalle Valo promiscuous mode via the Wireless Tool's Monitor mode. While in this 105367a1092SKalle Valo mode, no packets can be sent. 106367a1092SKalle Valo 107367a1092SKalle Valoconfig IPW2200_RADIOTAP 108367a1092SKalle Valo bool "Enable radiotap format 802.11 raw packet support" 109367a1092SKalle Valo depends on IPW2200_MONITOR 110367a1092SKalle Valo 111367a1092SKalle Valoconfig IPW2200_PROMISCUOUS 112367a1092SKalle Valo bool "Enable creation of a RF radiotap promiscuous interface" 113367a1092SKalle Valo depends on IPW2200_MONITOR 114367a1092SKalle Valo select IPW2200_RADIOTAP 115a7f7f624SMasahiro Yamada help 116367a1092SKalle Valo Enables the creation of a second interface prefixed 'rtap'. 117367a1092SKalle Valo This second interface will provide every received in radiotap 118367a1092SKalle Valo format. 119367a1092SKalle Valo 120367a1092SKalle Valo This is useful for performing wireless network analysis while 121367a1092SKalle Valo maintaining an active association. 122367a1092SKalle Valo 123367a1092SKalle Valo Example usage: 124367a1092SKalle Valo 125367a1092SKalle Valo % modprobe ipw2200 rtap_iface=1 126367a1092SKalle Valo % ifconfig rtap0 up 127367a1092SKalle Valo % tethereal -i rtap0 128367a1092SKalle Valo 129367a1092SKalle Valo If you do not specify 'rtap_iface=1' as a module parameter then 130367a1092SKalle Valo the rtap interface will not be created and you will need to turn 131367a1092SKalle Valo it on via sysfs: 132367a1092SKalle Valo 133367a1092SKalle Valo % echo 1 > /sys/bus/pci/drivers/ipw2200/*/rtap_iface 134367a1092SKalle Valo 135367a1092SKalle Valoconfig IPW2200_QOS 136367a1092SKalle Valo bool "Enable QoS support" 137367a1092SKalle Valo depends on IPW2200 138367a1092SKalle Valo 139367a1092SKalle Valoconfig IPW2200_DEBUG 140367a1092SKalle Valo bool "Enable full debugging output in IPW2200 module." 141367a1092SKalle Valo depends on IPW2200 142a7f7f624SMasahiro Yamada help 143367a1092SKalle Valo This option will enable low level debug tracing output for IPW2200. 144367a1092SKalle Valo 145367a1092SKalle Valo Note, normal debug code is already compiled in. This low level 146367a1092SKalle Valo debug option enables debug on hot paths (e.g Tx, Rx, ISR) and 147367a1092SKalle Valo will result in the kernel module being ~70 larger. Most users 148367a1092SKalle Valo will typically not need this high verbosity debug information. 149367a1092SKalle Valo 150367a1092SKalle Valo If you are not sure, say N here. 151367a1092SKalle Valo 152367a1092SKalle Valoconfig LIBIPW 153367a1092SKalle Valo tristate 154367a1092SKalle Valo depends on PCI && CFG80211 155367a1092SKalle Valo select WIRELESS_EXT 156367a1092SKalle Valo select CRYPTO 157367a1092SKalle Valo select CRYPTO_MICHAEL_MIC 158*5ab202f2SJohannes Berg select CRYPTO_LIB_ARC4 159367a1092SKalle Valo select CRC32 160a7f7f624SMasahiro Yamada help 161367a1092SKalle Valo This option enables the hardware independent IEEE 802.11 162367a1092SKalle Valo networking stack. This component is deprecated in favor of the 163367a1092SKalle Valo mac80211 component. 164367a1092SKalle Valo 165367a1092SKalle Valoconfig LIBIPW_DEBUG 166367a1092SKalle Valo bool "Full debugging output for the LIBIPW component" 167367a1092SKalle Valo depends on LIBIPW 168a7f7f624SMasahiro Yamada help 169367a1092SKalle Valo This option will enable debug tracing output for the 170367a1092SKalle Valo libipw component. 171367a1092SKalle Valo 172367a1092SKalle Valo This will result in the kernel module being ~70k larger. You 173367a1092SKalle Valo can control which debug output is sent to the kernel log by 174367a1092SKalle Valo setting the value in 175367a1092SKalle Valo 176367a1092SKalle Valo /proc/net/ieee80211/debug_level 177367a1092SKalle Valo 178367a1092SKalle Valo For example: 179367a1092SKalle Valo 180367a1092SKalle Valo % echo 0x00000FFO > /proc/net/ieee80211/debug_level 181367a1092SKalle Valo 182367a1092SKalle Valo For a list of values you can assign to debug_level, you 183367a1092SKalle Valo can look at the bit mask values in ieee80211.h 184367a1092SKalle Valo 185367a1092SKalle Valo If you are not trying to debug or develop the libipw 186367a1092SKalle Valo component, you most likely want to say N here. 187