1config IWLWIFI 2 tristate 3 4config IWLCORE 5 tristate "Intel Wireless Wifi Core" 6 depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL 7 select LIB80211 8 select IWLWIFI 9 select MAC80211_LEDS if IWLWIFI_LEDS 10 select LEDS_CLASS if IWLWIFI_LEDS 11 select RFKILL if IWLWIFI_RFKILL 12 13config IWLWIFI_LEDS 14 bool 15 default n 16 17config IWLWIFI_RFKILL 18 boolean "Iwlwifi RF kill support" 19 depends on IWLCORE 20 21config IWLWIFI_DEBUG 22 bool "Enable full debugging output in iwlagn driver" 23 depends on IWLCORE 24 ---help--- 25 This option will enable debug tracing output for the iwlwifi drivers 26 27 This will result in the kernel module being ~100k larger. You can 28 control which debug output is sent to the kernel log by setting the 29 value in 30 31 /sys/class/net/wlan0/device/debug_level 32 33 This entry will only exist if this option is enabled. 34 35 To set a value, simply echo an 8-byte hex value to the same file: 36 37 % echo 0x43fff > /sys/class/net/wlan0/device/debug_level 38 39 You can find the list of debug mask values in: 40 drivers/net/wireless/iwlwifi/iwl-debug.h 41 42 If this is your first time using this driver, you should say Y here 43 as the debug information can assist others in helping you resolve 44 any problems you may encounter. 45 46config IWLWIFI_DEBUGFS 47 bool "Iwlwifi debugfs support" 48 depends on IWLCORE && IWLWIFI_DEBUG && MAC80211_DEBUGFS 49 ---help--- 50 Enable creation of debugfs files for the iwlwifi drivers. 51 52config IWLAGN 53 tristate "Intel Wireless WiFi Next Gen AGN" 54 depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL 55 select FW_LOADER 56 select IWLCORE 57 ---help--- 58 Select to build the driver supporting the: 59 60 Intel Wireless WiFi Link Next-Gen AGN 61 62 This driver uses the kernel's mac80211 subsystem. 63 64 In order to use this driver, you will need a microcode (uCode) 65 image for it. You can obtain the microcode from: 66 67 <http://intellinuxwireless.org/>. 68 69 The microcode is typically installed in /lib/firmware. You can 70 look in the hotplug script /etc/hotplug/firmware.agent to 71 determine which directory FIRMWARE_DIR is set to when the script 72 runs. 73 74 If you want to compile the driver as a module ( = code which can be 75 inserted in and removed from the running kernel whenever you want), 76 say M here and read <file:Documentation/kbuild/modules.txt>. The 77 module will be called iwlagn.ko. 78 79config IWLAGN_SPECTRUM_MEASUREMENT 80 bool "Enable Spectrum Measurement in iwlagn driver" 81 depends on IWLAGN 82 ---help--- 83 This option will enable spectrum measurement for the iwlagn driver. 84 85config IWLAGN_LEDS 86 bool "Enable LEDS features in iwlagn driver" 87 depends on IWLAGN 88 select IWLWIFI_LEDS 89 ---help--- 90 This option enables LEDS for the iwlagn drivers 91 92 93config IWL4965 94 bool "Intel Wireless WiFi 4965AGN" 95 depends on IWLAGN 96 ---help--- 97 This option enables support for Intel Wireless WiFi Link 4965AGN 98 99config IWL5000 100 bool "Intel Wireless WiFi 5000AGN" 101 depends on IWLAGN 102 ---help--- 103 This option enables support for Intel Wireless WiFi Link 5000AGN Family 104 105config IWL3945 106 tristate "Intel PRO/Wireless 3945ABG/BG Network Connection" 107 depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL 108 select FW_LOADER 109 select LIB80211 110 select IWLWIFI 111 select MAC80211_LEDS if IWL3945_LEDS 112 select LEDS_CLASS if IWL3945_LEDS 113 select RFKILL if IWL3945_RFKILL 114 ---help--- 115 Select to build the driver supporting the: 116 117 Intel PRO/Wireless 3945ABG/BG Network Connection 118 119 This driver uses the kernel's mac80211 subsystem. 120 121 In order to use this driver, you will need a microcode (uCode) 122 image for it. You can obtain the microcode from: 123 124 <http://intellinuxwireless.org/>. 125 126 The microcode is typically installed in /lib/firmware. You can 127 look in the hotplug script /etc/hotplug/firmware.agent to 128 determine which directory FIRMWARE_DIR is set to when the script 129 runs. 130 131 If you want to compile the driver as a module ( = code which can be 132 inserted in and removed from the running kernel whenever you want), 133 say M here and read <file:Documentation/kbuild/modules.txt>. The 134 module will be called iwl3945.ko. 135 136config IWL3945_RFKILL 137 bool "Enable RF kill support in iwl3945 drivers" 138 depends on IWL3945 139 140config IWL3945_SPECTRUM_MEASUREMENT 141 bool "Enable Spectrum Measurement in iwl3945 drivers" 142 depends on IWL3945 143 ---help--- 144 This option will enable spectrum measurement for the iwl3945 driver. 145 146config IWL3945_LEDS 147 bool "Enable LEDS features in iwl3945 driver" 148 depends on IWL3945 149 ---help--- 150 This option enables LEDS for the iwl3945 driver. 151 152config IWL3945_DEBUG 153 bool "Enable full debugging output in iwl3945 driver" 154 depends on IWL3945 155 ---help--- 156 This option will enable debug tracing output for the iwl3945 157 driver. 158 159 This will result in the kernel module being ~100k larger. You can 160 control which debug output is sent to the kernel log by setting the 161 value in 162 163 /sys/bus/pci/drivers/${DRIVER}/debug_level 164 165 This entry will only exist if this option is enabled. 166 167 To set a value, simply echo an 8-byte hex value to the same file: 168 169 % echo 0x43fff > /sys/bus/pci/drivers/${DRIVER}/debug_level 170 171 You can find the list of debug mask values in: 172 drivers/net/wireless/iwlwifi/iwl-3945-debug.h 173 174 If this is your first time using this driver, you should say Y here 175 as the debug information can assist others in helping you resolve 176 any problems you may encounter. 177 178