Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux...
[deliverable/linux.git] / drivers / net / wireless / iwlwifi / Kconfig
1 config IWLWIFI
2 tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi) "
3 depends on PCI && MAC80211 && HAS_IOMEM
4 select FW_LOADER
5 select NEW_LEDS
6 select LEDS_CLASS
7 select LEDS_TRIGGERS
8 select MAC80211_LEDS
9 ---help---
10 Select to build the driver supporting the:
11
12 Intel Wireless WiFi Link Next-Gen AGN
13
14 This option enables support for use with the following hardware:
15 Intel Wireless WiFi Link 6250AGN Adapter
16 Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
17 Intel WiFi Link 1000BGN
18 Intel Wireless WiFi 5150AGN
19 Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
20 Intel 6005 Series Wi-Fi Adapters
21 Intel 6030 Series Wi-Fi Adapters
22 Intel Wireless WiFi Link 6150BGN 2 Adapter
23 Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
24 Intel 2000 Series Wi-Fi Adapters
25 Intel 7260 Wi-Fi Adapter
26 Intel 3160 Wi-Fi Adapter
27
28
29 This driver uses the kernel's mac80211 subsystem.
30
31 In order to use this driver, you will need a microcode (uCode)
32 image for it. You can obtain the microcode from:
33
34 <http://intellinuxwireless.org/>.
35
36 The microcode is typically installed in /lib/firmware. You can
37 look in the hotplug script /etc/hotplug/firmware.agent to
38 determine which directory FIRMWARE_DIR is set to when the script
39 runs.
40
41 If you want to compile the driver as a module ( = code which can be
42 inserted in and removed from the running kernel whenever you want),
43 say M here and read <file:Documentation/kbuild/modules.txt>. The
44 module will be called iwlwifi.
45
46 config IWLDVM
47 tristate "Intel Wireless WiFi DVM Firmware support"
48 depends on IWLWIFI
49 default IWLWIFI
50 help
51 This is the driver that supports the DVM firmware which is
52 used by most existing devices (with the exception of 7260
53 and 3160).
54
55 config IWLMVM
56 tristate "Intel Wireless WiFi MVM Firmware support"
57 depends on IWLWIFI
58 help
59 This is the driver that supports the MVM firmware which is
60 currently only available for 7260 and 3160 devices.
61
62 # don't call it _MODULE -- will confuse Kconfig/fixdep/...
63 config IWLWIFI_OPMODE_MODULAR
64 bool
65 default y if IWLDVM=m
66 default y if IWLMVM=m
67
68 comment "WARNING: iwlwifi is useless without IWLDVM or IWLMVM"
69 depends on IWLWIFI && IWLDVM=n && IWLMVM=n
70
71 menu "Debugging Options"
72 depends on IWLWIFI
73
74 config IWLWIFI_DEBUG
75 bool "Enable full debugging output in the iwlwifi driver"
76 depends on IWLWIFI
77 ---help---
78 This option will enable debug tracing output for the iwlwifi drivers
79
80 This will result in the kernel module being ~100k larger. You can
81 control which debug output is sent to the kernel log by setting the
82 value in
83
84 /sys/module/iwlwifi/parameters/debug
85
86 This entry will only exist if this option is enabled.
87
88 To set a value, simply echo an 8-byte hex value to the same file:
89
90 % echo 0x43fff > /sys/module/iwlwifi/parameters/debug
91
92 You can find the list of debug mask values in:
93 drivers/net/wireless/iwlwifi/iwl-debug.h
94
95 If this is your first time using this driver, you should say Y here
96 as the debug information can assist others in helping you resolve
97 any problems you may encounter.
98
99 config IWLWIFI_DEBUGFS
100 bool "iwlwifi debugfs support"
101 depends on IWLWIFI && MAC80211_DEBUGFS
102 ---help---
103 Enable creation of debugfs files for the iwlwifi drivers. This
104 is a low-impact option that allows getting insight into the
105 driver's state at runtime.
106
107 config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE
108 bool "Experimental uCode support"
109 depends on IWLWIFI && IWLWIFI_DEBUG
110 ---help---
111 Enable use of experimental ucode for testing and debugging.
112
113 config IWLWIFI_DEVICE_TRACING
114 bool "iwlwifi device access tracing"
115 depends on IWLWIFI
116 depends on EVENT_TRACING
117 help
118 Say Y here to trace all commands, including TX frames and IO
119 accesses, sent to the device. If you say yes, iwlwifi will
120 register with the ftrace framework for event tracing and dump
121 all this information to the ringbuffer, you may need to
122 increase the ringbuffer size. See the ftrace documentation
123 for more information.
124
125 When tracing is not enabled, this option still has some
126 (though rather small) overhead.
127
128 If unsure, say Y so we can help you better when problems
129 occur.
130 endmenu
This page took 0.034921 seconds and 6 git commands to generate.