9 menu "Debugging Options"
10 depends on IWLWIFI_LEGACY
12 config IWLWIFI_LEGACY_DEBUG
13 bool "Enable full debugging output in 4965 and 3945 drivers"
14 depends on IWLWIFI_LEGACY
16 This option will enable debug tracing output for the iwlwifilegacy
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/iwlwifilegacy/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_LEGACY_DEBUGFS
39 bool "4965 and 3945 debugfs support"
40 depends on IWLWIFI_LEGACY && MAC80211_DEBUGFS
42 Enable creation of debugfs files for the iwlwifilegacy drivers. This
43 is a low-impact option that allows getting insight into the
44 driver's state at runtime.
46 config IWLWIFI_LEGACY_DEVICE_TRACING
47 bool "iwlwifilegacy legacy device access tracing"
48 depends on IWLWIFI_LEGACY
49 depends on EVENT_TRACING
51 Say Y here to trace all commands, including TX frames and IO
52 accesses, sent to the device. If you say yes, iwlwifilegacy will
53 register with the ftrace framework for event tracing and dump
54 all this information to the ringbuffer, you may need to
55 increase the ringbuffer size. See the ftrace documentation
58 When tracing is not enabled, this option still has some
59 (though rather small) overhead.
61 If unsure, say Y so we can help you better when problems
66 tristate "Intel Wireless WiFi 4965AGN (iwl4965)"
67 depends on PCI && MAC80211
70 This option enables support for
72 Select to build the driver supporting the:
74 Intel Wireless WiFi Link 4965AGN
76 This driver uses the kernel's mac80211 subsystem.
78 In order to use this driver, you will need a microcode (uCode)
79 image for it. You can obtain the microcode from:
81 <http://intellinuxwireless.org/>.
83 The microcode is typically installed in /lib/firmware. You can
84 look in the hotplug script /etc/hotplug/firmware.agent to
85 determine which directory FIRMWARE_DIR is set to when the script
88 If you want to compile the driver as a module ( = code which can be
89 inserted in and removed from the running kernel whenever you want),
90 say M here and read <file:Documentation/kbuild/modules.txt>. The
91 module will be called iwl4965.
94 tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)"
95 depends on PCI && MAC80211
98 Select to build the driver supporting the:
100 Intel PRO/Wireless 3945ABG/BG Network Connection
102 This driver uses the kernel's mac80211 subsystem.
104 In order to use this driver, you will need a microcode (uCode)
105 image for it. You can obtain the microcode from:
107 <http://intellinuxwireless.org/>.
109 The microcode is typically installed in /lib/firmware. You can
110 look in the hotplug script /etc/hotplug/firmware.agent to
111 determine which directory FIRMWARE_DIR is set to when the script
114 If you want to compile the driver as a module ( = code which can be
115 inserted in and removed from the running kernel whenever you want),
116 say M here and read <file:Documentation/kbuild/modules.txt>. The
117 module will be called iwl3945.