2 tristate "Intel Wireless Wifi"
3 depends on PCI && MAC80211
10 menu "Debugging Options"
14 bool "Enable full debugging output in iwlagn and iwl3945 drivers"
17 This option will enable debug tracing output for the iwlwifi drivers
19 This will result in the kernel module being ~100k larger. You can
20 control which debug output is sent to the kernel log by setting the
23 /sys/class/net/wlan0/device/debug_level
25 This entry will only exist if this option is enabled.
27 To set a value, simply echo an 8-byte hex value to the same file:
29 % echo 0x43fff > /sys/class/net/wlan0/device/debug_level
31 You can find the list of debug mask values in:
32 drivers/net/wireless/iwlwifi/iwl-debug.h
34 If this is your first time using this driver, you should say Y here
35 as the debug information can assist others in helping you resolve
36 any problems you may encounter.
38 config IWLWIFI_DEBUGFS
39 bool "iwlagn debugfs support"
40 depends on IWLWIFI && MAC80211_DEBUGFS
42 Enable creation of debugfs files for the iwlwifi drivers. This
43 is a low-impact option that allows getting insight into the
44 driver's state at runtime.
46 config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE
47 bool "Experimental uCode support"
48 depends on IWLWIFI && IWLWIFI_DEBUG
50 Enable use of experimental ucode for testing and debugging.
52 config IWLWIFI_DEVICE_TRACING
53 bool "iwlwifi device access tracing"
55 depends on EVENT_TRACING
57 Say Y here to trace all commands, including TX frames and IO
58 accesses, sent to the device. If you say yes, iwlwifi will
59 register with the ftrace framework for event tracing and dump
60 all this information to the ringbuffer, you may need to
61 increase the ringbuffer size. See the ftrace documentation
64 When tracing is not enabled, this option still has some
65 (though rather small) overhead.
67 If unsure, say Y so we can help you better when problems
72 tristate "Intel Wireless WiFi Next Gen AGN (iwlagn)"
75 Select to build the driver supporting the:
77 Intel Wireless WiFi Link Next-Gen AGN
79 This driver uses the kernel's mac80211 subsystem.
81 In order to use this driver, you will need a microcode (uCode)
82 image for it. You can obtain the microcode from:
84 <http://intellinuxwireless.org/>.
86 The microcode is typically installed in /lib/firmware. You can
87 look in the hotplug script /etc/hotplug/firmware.agent to
88 determine which directory FIRMWARE_DIR is set to when the script
91 If you want to compile the driver as a module ( = code which can be
92 inserted in and removed from the running kernel whenever you want),
93 say M here and read <file:Documentation/kbuild/modules.txt>. The
94 module will be called iwlagn.
98 bool "Intel Wireless WiFi 4965AGN"
101 This option enables support for Intel Wireless WiFi Link 4965AGN
104 bool "Intel Wireless-N/Advanced-N/Ultimate-N WiFi Link"
107 This option enables support for use with the following hardware:
108 Intel Wireless WiFi Link 6250AGN Adapter
109 Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
110 Intel WiFi Link 1000BGN
111 Intel Wireless WiFi 5150AGN
112 Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
113 Intel 6005 Series Wi-Fi Adapters
114 Intel 6030 Series Wi-Fi Adapters
115 Intel Wireless WiFi Link 6150BGN 2 Adapter
116 Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
117 Intel 2000 Series Wi-Fi Adapters
120 bool "iwlwifi experimental P2P support"
123 This option enables experimental P2P support for some devices
124 based on microcode support. Since P2P support is still under
125 development, this option may even enable it for some devices
126 now that turn out to not support it in the future due to
127 microcode restrictions.
129 To determine if your microcode supports the experimental P2P
130 offered by this option, check if the driver advertises AP
131 support when it is loaded.
133 Say Y only if you want to experiment with P2P.
136 tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)"
139 Select to build the driver supporting the:
141 Intel PRO/Wireless 3945ABG/BG Network Connection
143 This driver uses the kernel's mac80211 subsystem.
145 In order to use this driver, you will need a microcode (uCode)
146 image for it. You can obtain the microcode from:
148 <http://intellinuxwireless.org/>.
150 The microcode is typically installed in /lib/firmware. You can
151 look in the hotplug script /etc/hotplug/firmware.agent to
152 determine which directory FIRMWARE_DIR is set to when the script
155 If you want to compile the driver as a module ( = code which can be
156 inserted in and removed from the running kernel whenever you want),
157 say M here and read <file:Documentation/kbuild/modules.txt>. The
158 module will be called iwl3945.