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