2 tristate "Intel Wireless Wifi"
3 depends on PCI && MAC80211
6 menu "Debugging Options"
10 bool "Enable full debugging output in iwlagn and iwl3945 drivers"
13 This option will enable debug tracing output for the iwlwifi drivers
15 This will result in the kernel module being ~100k larger. You can
16 control which debug output is sent to the kernel log by setting the
19 /sys/class/net/wlan0/device/debug_level
21 This entry will only exist if this option is enabled.
23 To set a value, simply echo an 8-byte hex value to the same file:
25 % echo 0x43fff > /sys/class/net/wlan0/device/debug_level
27 You can find the list of debug mask values in:
28 drivers/net/wireless/iwlwifi/iwl-debug.h
30 If this is your first time using this driver, you should say Y here
31 as the debug information can assist others in helping you resolve
32 any problems you may encounter.
34 config IWLWIFI_DEBUGFS
35 bool "iwlagn debugfs support"
36 depends on IWLWIFI && MAC80211_DEBUGFS
38 Enable creation of debugfs files for the iwlwifi drivers. This
39 is a low-impact option that allows getting insight into the
40 driver's state at runtime.
42 config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE
43 bool "Experimental uCode support"
44 depends on IWLWIFI && IWLWIFI_DEBUG
46 Enable use of experimental ucode for testing and debugging.
48 config IWLWIFI_DEVICE_TRACING
49 bool "iwlwifi device access tracing"
51 depends on EVENT_TRACING
53 Say Y here to trace all commands, including TX frames and IO
54 accesses, sent to the device. If you say yes, iwlwifi will
55 register with the ftrace framework for event tracing and dump
56 all this information to the ringbuffer, you may need to
57 increase the ringbuffer size. See the ftrace documentation
60 When tracing is not enabled, this option still has some
61 (though rather small) overhead.
63 If unsure, say Y so we can help you better when problems
68 tristate "Intel Wireless WiFi Next Gen AGN (iwlagn)"
71 Select to build the driver supporting the:
73 Intel Wireless WiFi Link Next-Gen AGN
75 This driver uses the kernel's mac80211 subsystem.
77 In order to use this driver, you will need a microcode (uCode)
78 image for it. You can obtain the microcode from:
80 <http://intellinuxwireless.org/>.
82 The microcode is typically installed in /lib/firmware. You can
83 look in the hotplug script /etc/hotplug/firmware.agent to
84 determine which directory FIRMWARE_DIR is set to when the script
87 If you want to compile the driver as a module ( = code which can be
88 inserted in and removed from the running kernel whenever you want),
89 say M here and read <file:Documentation/kbuild/modules.txt>. The
90 module will be called iwlagn.
94 bool "Intel Wireless WiFi 4965AGN"
97 This option enables support for Intel Wireless WiFi Link 4965AGN
100 bool "Intel Wireless-N/Advanced-N/Ultimate-N WiFi Link"
103 This option enables support for use with the following hardware:
104 Intel Wireless WiFi Link 6250AGN Adapter
105 Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
106 Intel WiFi Link 1000BGN
107 Intel Wireless WiFi 5150AGN
108 Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
111 tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)"
114 Select to build the driver supporting the:
116 Intel PRO/Wireless 3945ABG/BG Network Connection
118 This driver uses the kernel's mac80211 subsystem.
120 In order to use this driver, you will need a microcode (uCode)
121 image for it. You can obtain the microcode from:
123 <http://intellinuxwireless.org/>.
125 The microcode is typically installed in /lib/firmware. You can
126 look in the hotplug script /etc/hotplug/firmware.agent to
127 determine which directory FIRMWARE_DIR is set to when the script
130 If you want to compile the driver as a module ( = code which can be
131 inserted in and removed from the running kernel whenever you want),
132 say M here and read <file:Documentation/kbuild/modules.txt>. The
133 module will be called iwl3945.