2 tristate "Intel Wireless Wifi"
3 depends on PCI && MAC80211
7 bool "Enable full debugging output in iwlagn and iwl3945 drivers"
10 This option will enable debug tracing output for the iwlwifi drivers
12 This will result in the kernel module being ~100k larger. You can
13 control which debug output is sent to the kernel log by setting the
16 /sys/class/net/wlan0/device/debug_level
18 This entry will only exist if this option is enabled.
20 To set a value, simply echo an 8-byte hex value to the same file:
22 % echo 0x43fff > /sys/class/net/wlan0/device/debug_level
24 You can find the list of debug mask values in:
25 drivers/net/wireless/iwlwifi/iwl-debug.h
27 If this is your first time using this driver, you should say Y here
28 as the debug information can assist others in helping you resolve
29 any problems you may encounter.
31 config IWLWIFI_DEBUGFS
32 bool "iwlagn debugfs support"
33 depends on IWLWIFI && IWLWIFI_DEBUG && MAC80211_DEBUGFS
35 Enable creation of debugfs files for the iwlwifi drivers.
37 config IWLWIFI_DEVICE_TRACING
38 bool "iwlwifi device access tracing"
40 depends on EVENT_TRACING
42 Say Y here to trace all commands, including TX frames and IO
43 accesses, sent to the device. If you say yes, iwlwifi will
44 register with the ftrace framework for event tracing and dump
45 all this information to the ringbuffer, you may need to
46 increase the ringbuffer size. See the ftrace documentation
49 When tracing is not enabled, this option still has some
50 (though rather small) overhead.
52 If unsure, say Y so we can help you better when problems
56 tristate "Intel Wireless WiFi Next Gen AGN (iwlagn)"
59 Select to build the driver supporting the:
61 Intel Wireless WiFi Link Next-Gen AGN
63 This driver uses the kernel's mac80211 subsystem.
65 In order to use this driver, you will need a microcode (uCode)
66 image for it. You can obtain the microcode from:
68 <http://intellinuxwireless.org/>.
70 The microcode is typically installed in /lib/firmware. You can
71 look in the hotplug script /etc/hotplug/firmware.agent to
72 determine which directory FIRMWARE_DIR is set to when the script
75 If you want to compile the driver as a module ( = code which can be
76 inserted in and removed from the running kernel whenever you want),
77 say M here and read <file:Documentation/kbuild/modules.txt>. The
78 module will be called iwlagn.
82 bool "Intel Wireless WiFi 4965AGN"
85 This option enables support for Intel Wireless WiFi Link 4965AGN
88 bool "Intel Wireless WiFi 5000AGN; Intel WiFi Link 1000, 6000, and 6050 Series"
91 This option enables support for Intel Wireless WiFi Link 5000AGN Family
94 tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)"
97 Select to build the driver supporting the:
99 Intel PRO/Wireless 3945ABG/BG Network Connection
101 This driver uses the kernel's mac80211 subsystem.
103 In order to use this driver, you will need a microcode (uCode)
104 image for it. You can obtain the microcode from:
106 <http://intellinuxwireless.org/>.
108 The microcode is typically installed in /lib/firmware. You can
109 look in the hotplug script /etc/hotplug/firmware.agent to
110 determine which directory FIRMWARE_DIR is set to when the script
113 If you want to compile the driver as a module ( = code which can be
114 inserted in and removed from the running kernel whenever you want),
115 say M here and read <file:Documentation/kbuild/modules.txt>. The
116 module will be called iwl3945.