1config IWLWIFI 2 tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi) " 3 depends on PCI && MAC80211 && HAS_IOMEM 4 select FW_LOADER 5 select NEW_LEDS 6 select LEDS_CLASS 7 select LEDS_TRIGGERS 8 select MAC80211_LEDS 9 ---help--- 10 Select to build the driver supporting the: 11 12 Intel Wireless WiFi Link Next-Gen AGN 13 14 This option enables support for use with the following hardware: 15 Intel Wireless WiFi Link 6250AGN Adapter 16 Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN) 17 Intel WiFi Link 1000BGN 18 Intel Wireless WiFi 5150AGN 19 Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN 20 Intel 6005 Series Wi-Fi Adapters 21 Intel 6030 Series Wi-Fi Adapters 22 Intel Wireless WiFi Link 6150BGN 2 Adapter 23 Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN) 24 Intel 2000 Series Wi-Fi Adapters 25 26 27 This driver uses the kernel's mac80211 subsystem. 28 29 In order to use this driver, you will need a microcode (uCode) 30 image for it. You can obtain the microcode from: 31 32 <http://intellinuxwireless.org/>. 33 34 The microcode is typically installed in /lib/firmware. You can 35 look in the hotplug script /etc/hotplug/firmware.agent to 36 determine which directory FIRMWARE_DIR is set to when the script 37 runs. 38 39 If you want to compile the driver as a module ( = code which can be 40 inserted in and removed from the running kernel whenever you want), 41 say M here and read <file:Documentation/kbuild/modules.txt>. The 42 module will be called iwlwifi. 43 44config IWLDVM 45 tristate "Intel Wireless WiFi DVM Firmware support" 46 depends on IWLWIFI 47 default IWLWIFI 48 help 49 This is the driver supporting the DVM firmware which is 50 currently the only firmware available for existing devices. 51 52config IWLMVM 53 tristate "Intel Wireless WiFi MVM Firmware support" 54 depends on IWLWIFI 55 help 56 This is the driver supporting the MVM firmware which is 57 currently only available for 7000 series devices. 58 59 Say yes if you have such a device. 60 61# don't call it _MODULE -- will confuse Kconfig/fixdep/... 62config IWLWIFI_OPMODE_MODULAR 63 bool 64 default y if IWLDVM=m 65 default y if IWLMVM=m 66 67comment "WARNING: iwlwifi is useless without IWLDVM or IWLMVM" 68 depends on IWLWIFI && IWLDVM=n && IWLMVM=n 69 70menu "Debugging Options" 71 depends on IWLWIFI 72 73config IWLWIFI_DEBUG 74 bool "Enable full debugging output in the iwlwifi driver" 75 depends on IWLWIFI 76 ---help--- 77 This option will enable debug tracing output for the iwlwifi drivers 78 79 This will result in the kernel module being ~100k larger. You can 80 control which debug output is sent to the kernel log by setting the 81 value in 82 83 /sys/module/iwlwifi/parameters/debug 84 85 This entry will only exist if this option is enabled. 86 87 To set a value, simply echo an 8-byte hex value to the same file: 88 89 % echo 0x43fff > /sys/module/iwlwifi/parameters/debug 90 91 You can find the list of debug mask values in: 92 drivers/net/wireless/iwlwifi/iwl-debug.h 93 94 If this is your first time using this driver, you should say Y here 95 as the debug information can assist others in helping you resolve 96 any problems you may encounter. 97 98config IWLWIFI_DEBUGFS 99 bool "iwlwifi debugfs support" 100 depends on IWLWIFI && MAC80211_DEBUGFS 101 ---help--- 102 Enable creation of debugfs files for the iwlwifi drivers. This 103 is a low-impact option that allows getting insight into the 104 driver's state at runtime. 105 106config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE 107 bool "Experimental uCode support" 108 depends on IWLWIFI && IWLWIFI_DEBUG 109 ---help--- 110 Enable use of experimental ucode for testing and debugging. 111 112config IWLWIFI_DEVICE_TRACING 113 bool "iwlwifi device access tracing" 114 depends on IWLWIFI 115 depends on EVENT_TRACING 116 help 117 Say Y here to trace all commands, including TX frames and IO 118 accesses, sent to the device. If you say yes, iwlwifi will 119 register with the ftrace framework for event tracing and dump 120 all this information to the ringbuffer, you may need to 121 increase the ringbuffer size. See the ftrace documentation 122 for more information. 123 124 When tracing is not enabled, this option still has some 125 (though rather small) overhead. 126 127 If unsure, say Y so we can help you better when problems 128 occur. 129endmenu 130 131config IWLWIFI_DEVICE_TESTMODE 132 def_bool y 133 depends on IWLWIFI 134 depends on NL80211_TESTMODE 135 help 136 This option enables the testmode support for iwlwifi device through 137 NL80211_TESTMODE. This provide the capabilities of enable user space 138 validation applications to interacts with the device through the 139 generic netlink message via NL80211_TESTMODE channel. 140 141config IWLWIFI_P2P 142 def_bool y 143 bool "iwlwifi experimental P2P support" 144 depends on IWLWIFI 145 help 146 This option enables experimental P2P support for some devices 147 based on microcode support. Since P2P support is still under 148 development, this option may even enable it for some devices 149 now that turn out to not support it in the future due to 150 microcode restrictions. 151 152 To determine if your microcode supports the experimental P2P 153 offered by this option, check if the driver advertises AP 154 support when it is loaded. 155 156 Say Y only if you want to experiment with P2P. 157