Commit | Line | Data |
---|---|---|
3c607d27 DF |
1 | config IWLWIFI |
2 | tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi) " | |
05f5b97e | 3 | depends on PCI && MAC80211 && HAS_IOMEM |
80bc5393 | 4 | select FW_LOADER |
5ed540ae WYG |
5 | select NEW_LEDS |
6 | select LEDS_CLASS | |
7 | select LEDS_TRIGGERS | |
8 | select MAC80211_LEDS | |
cc5f7e39 | 9 | select IWLDVM |
be663ab6 WYG |
10 | ---help--- |
11 | Select to build the driver supporting the: | |
12 | ||
13 | Intel Wireless WiFi Link Next-Gen AGN | |
14 | ||
15 | This option enables support for use with the following hardware: | |
16 | Intel Wireless WiFi Link 6250AGN Adapter | |
17 | Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN) | |
18 | Intel WiFi Link 1000BGN | |
19 | Intel Wireless WiFi 5150AGN | |
20 | Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN | |
21 | Intel 6005 Series Wi-Fi Adapters | |
22 | Intel 6030 Series Wi-Fi Adapters | |
23 | Intel Wireless WiFi Link 6150BGN 2 Adapter | |
24 | Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN) | |
25 | Intel 2000 Series Wi-Fi Adapters | |
26 | ||
27 | ||
28 | This driver uses the kernel's mac80211 subsystem. | |
29 | ||
30 | In order to use this driver, you will need a microcode (uCode) | |
31 | image for it. You can obtain the microcode from: | |
32 | ||
33 | <http://intellinuxwireless.org/>. | |
34 | ||
35 | The microcode is typically installed in /lib/firmware. You can | |
36 | look in the hotplug script /etc/hotplug/firmware.agent to | |
37 | determine which directory FIRMWARE_DIR is set to when the script | |
38 | runs. | |
39 | ||
40 | If you want to compile the driver as a module ( = code which can be | |
41 | inserted in and removed from the running kernel whenever you want), | |
42 | say M here and read <file:Documentation/kbuild/modules.txt>. The | |
3c607d27 | 43 | module will be called iwlwifi. |
ab53d8af | 44 | |
cc5f7e39 | 45 | config IWLDVM |
8ca151b5 | 46 | tristate "Intel Wireless WiFi DVM Firmware support" |
cc5f7e39 | 47 | depends on IWLWIFI |
8ca151b5 JB |
48 | help |
49 | This is the driver supporting the DVM firmware which is | |
50 | currently the only firmware available for existing devices. | |
51 | ||
52 | config IWLMVM | |
53 | tristate "Intel Wireless WiFi MVM Firmware support" | |
54 | depends on IWLWIFI | |
55 | help | |
56 | This is the driver supporting the MVM firmware which is | |
57 | currently only available for 7000 series devices. | |
58 | ||
59 | Say yes if you have such a device. | |
cc5f7e39 | 60 | |
110ff6db | 61 | menu "Debugging Options" |
3c607d27 | 62 | depends on IWLWIFI |
110ff6db | 63 | |
4fc22b21 | 64 | config IWLWIFI_DEBUG |
3c607d27 DF |
65 | bool "Enable full debugging output in the iwlwifi driver" |
66 | depends on IWLWIFI | |
4fc22b21 TW |
67 | ---help--- |
68 | This option will enable debug tracing output for the iwlwifi drivers | |
69 | ||
70 | This will result in the kernel module being ~100k larger. You can | |
71 | control which debug output is sent to the kernel log by setting the | |
72 | value in | |
73 | ||
add6ff1a | 74 | /sys/module/iwlwifi/parameters/debug |
4fc22b21 TW |
75 | |
76 | This entry will only exist if this option is enabled. | |
77 | ||
78 | To set a value, simply echo an 8-byte hex value to the same file: | |
79 | ||
add6ff1a | 80 | % echo 0x43fff > /sys/module/iwlwifi/parameters/debug |
4fc22b21 TW |
81 | |
82 | You can find the list of debug mask values in: | |
83 | drivers/net/wireless/iwlwifi/iwl-debug.h | |
84 | ||
85 | If this is your first time using this driver, you should say Y here | |
86 | as the debug information can assist others in helping you resolve | |
87 | any problems you may encounter. | |
88 | ||
89 | config IWLWIFI_DEBUGFS | |
3c607d27 DF |
90 | bool "iwlwifi debugfs support" |
91 | depends on IWLWIFI && MAC80211_DEBUGFS | |
4fc22b21 | 92 | ---help--- |
d73e4923 JB |
93 | Enable creation of debugfs files for the iwlwifi drivers. This |
94 | is a low-impact option that allows getting insight into the | |
95 | driver's state at runtime. | |
4fc22b21 | 96 | |
39396085 JS |
97 | config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE |
98 | bool "Experimental uCode support" | |
3c607d27 | 99 | depends on IWLWIFI && IWLWIFI_DEBUG |
39396085 JS |
100 | ---help--- |
101 | Enable use of experimental ucode for testing and debugging. | |
102 | ||
be1a71a1 JB |
103 | config IWLWIFI_DEVICE_TRACING |
104 | bool "iwlwifi device access tracing" | |
3c607d27 | 105 | depends on IWLWIFI |
be1a71a1 JB |
106 | depends on EVENT_TRACING |
107 | help | |
108 | Say Y here to trace all commands, including TX frames and IO | |
109 | accesses, sent to the device. If you say yes, iwlwifi will | |
110 | register with the ftrace framework for event tracing and dump | |
111 | all this information to the ringbuffer, you may need to | |
112 | increase the ringbuffer size. See the ftrace documentation | |
113 | for more information. | |
114 | ||
115 | When tracing is not enabled, this option still has some | |
116 | (though rather small) overhead. | |
117 | ||
118 | If unsure, say Y so we can help you better when problems | |
119 | occur. | |
110ff6db | 120 | endmenu |
be1a71a1 | 121 | |
5ef15ccc | 122 | config IWLWIFI_DEVICE_TESTMODE |
fe67c084 | 123 | def_bool y |
3c607d27 | 124 | depends on IWLWIFI |
fe67c084 | 125 | depends on NL80211_TESTMODE |
4613e72d | 126 | help |
5ef15ccc WYG |
127 | This option enables the testmode support for iwlwifi device through |
128 | NL80211_TESTMODE. This provide the capabilities of enable user space | |
129 | validation applications to interacts with the device through the | |
130 | generic netlink message via NL80211_TESTMODE channel. | |
0cb38d65 WYG |
131 | |
132 | config IWLWIFI_P2P | |
ef213d6d WYG |
133 | def_bool y |
134 | bool "iwlwifi experimental P2P support" | |
135 | depends on IWLWIFI | |
136 | help | |
137 | This option enables experimental P2P support for some devices | |
138 | based on microcode support. Since P2P support is still under | |
139 | development, this option may even enable it for some devices | |
140 | now that turn out to not support it in the future due to | |
141 | microcode restrictions. | |
142 | ||
143 | To determine if your microcode supports the experimental P2P | |
144 | offered by this option, check if the driver advertises AP | |
145 | support when it is loaded. | |
146 | ||
147 | Say Y only if you want to experiment with P2P. |