2 tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi) "
3 depends on PCI && MAC80211 && HAS_IOMEM
6 Select to build the driver supporting the:
8 Intel Wireless WiFi Link Next-Gen AGN
10 This option enables support for use with the following hardware:
11 Intel Wireless WiFi Link 6250AGN Adapter
12 Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
13 Intel WiFi Link 1000BGN
14 Intel Wireless WiFi 5150AGN
15 Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
16 Intel 6005 Series Wi-Fi Adapters
17 Intel 6030 Series Wi-Fi Adapters
18 Intel Wireless WiFi Link 6150BGN 2 Adapter
19 Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
20 Intel 2000 Series Wi-Fi Adapters
21 Intel 7260 Wi-Fi Adapter
22 Intel 3160 Wi-Fi Adapter
23 Intel 7265 Wi-Fi Adapter
26 This driver uses the kernel's mac80211 subsystem.
28 In order to use this driver, you will need a firmware
29 image for it. You can obtain the microcode from:
31 <http://wireless.kernel.org/en/users/Drivers/iwlwifi>.
33 The firmware is typically installed in /lib/firmware. You can
34 look in the hotplug script /etc/hotplug/firmware.agent to
35 determine which directory FIRMWARE_DIR is set to when the script
38 If you want to compile the driver as a module ( = code which can be
39 inserted in and removed from the running kernel whenever you want),
40 say M here and read <file:Documentation/kbuild/modules.txt>. The
41 module will be called iwlwifi.
47 depends on LEDS_CLASS=y || LEDS_CLASS=IWLWIFI
53 tristate "Intel Wireless WiFi DVM Firmware support"
56 This is the driver that supports the DVM firmware which is
57 used by most existing devices (with the exception of 7260
61 tristate "Intel Wireless WiFi MVM Firmware support"
63 This is the driver that supports the MVM firmware which is
64 currently only available for 7260 and 3160 devices.
66 # don't call it _MODULE -- will confuse Kconfig/fixdep/...
67 config IWLWIFI_OPMODE_MODULAR
72 comment "WARNING: iwlwifi is useless without IWLDVM or IWLMVM"
73 depends on IWLDVM=n && IWLMVM=n
75 config IWLWIFI_BCAST_FILTERING
76 bool "Enable broadcast filtering"
79 Say Y here to enable default bcast filtering configuration.
81 Enabling broadcast filtering will drop any incoming wireless
82 broadcast frames, except some very specific predefined
83 patterns (e.g. incoming arp requests).
85 If unsure, don't enable this option, as some programs might
86 expect incoming broadcasts for their normal operations.
89 bool "enable U-APSD by default"
92 Say Y here to enable U-APSD by default. This may cause
93 interoperability problems with some APs, manifesting in lower than
94 expected throughput due to those APs not enabling aggregation
98 menu "Debugging Options"
101 bool "Enable full debugging output in the iwlwifi driver"
103 This option will enable debug tracing output for the iwlwifi drivers
105 This will result in the kernel module being ~100k larger. You can
106 control which debug output is sent to the kernel log by setting the
109 /sys/module/iwlwifi/parameters/debug
111 This entry will only exist if this option is enabled.
113 To set a value, simply echo an 8-byte hex value to the same file:
115 % echo 0x43fff > /sys/module/iwlwifi/parameters/debug
117 You can find the list of debug mask values in:
118 drivers/net/wireless/iwlwifi/iwl-debug.h
120 If this is your first time using this driver, you should say Y here
121 as the debug information can assist others in helping you resolve
122 any problems you may encounter.
124 config IWLWIFI_DEBUGFS
125 bool "iwlwifi debugfs support"
126 depends on MAC80211_DEBUGFS
128 Enable creation of debugfs files for the iwlwifi drivers. This
129 is a low-impact option that allows getting insight into the
130 driver's state at runtime.
132 config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE
133 bool "Experimental uCode support"
134 depends on IWLWIFI_DEBUG
136 Enable use of experimental ucode for testing and debugging.
138 config IWLWIFI_DEVICE_TRACING
139 bool "iwlwifi device access tracing"
140 depends on EVENT_TRACING
142 Say Y here to trace all commands, including TX frames and IO
143 accesses, sent to the device. If you say yes, iwlwifi will
144 register with the ftrace framework for event tracing and dump
145 all this information to the ringbuffer, you may need to
146 increase the ringbuffer size. See the ftrace documentation
147 for more information.
149 When tracing is not enabled, this option still has some
150 (though rather small) overhead.
152 If unsure, say Y so we can help you better when problems