]>
Commit | Line | Data |
---|---|---|
358c1295 | 1 | config IWLWIFI |
80bc5393 | 2 | tristate "Intel Wireless Wifi" |
1d8c4ae9 | 3 | depends on PCI && MAC80211 |
80bc5393 | 4 | select FW_LOADER |
ab53d8af | 5 | |
4fc22b21 | 6 | config IWLWIFI_DEBUG |
d08853a3 | 7 | bool "Enable full debugging output in iwlagn and iwl3945 drivers" |
80bc5393 | 8 | depends on IWLWIFI |
4fc22b21 TW |
9 | ---help--- |
10 | This option will enable debug tracing output for the iwlwifi drivers | |
11 | ||
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 | |
14 | value in | |
15 | ||
16 | /sys/class/net/wlan0/device/debug_level | |
17 | ||
18 | This entry will only exist if this option is enabled. | |
19 | ||
20 | To set a value, simply echo an 8-byte hex value to the same file: | |
21 | ||
22 | % echo 0x43fff > /sys/class/net/wlan0/device/debug_level | |
23 | ||
24 | You can find the list of debug mask values in: | |
25 | drivers/net/wireless/iwlwifi/iwl-debug.h | |
26 | ||
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. | |
30 | ||
31 | config IWLWIFI_DEBUGFS | |
80bc5393 | 32 | bool "iwlagn debugfs support" |
d73e4923 | 33 | depends on IWLWIFI && MAC80211_DEBUGFS |
4fc22b21 | 34 | ---help--- |
d73e4923 JB |
35 | Enable creation of debugfs files for the iwlwifi drivers. This |
36 | is a low-impact option that allows getting insight into the | |
37 | driver's state at runtime. | |
4fc22b21 | 38 | |
be1a71a1 JB |
39 | config IWLWIFI_DEVICE_TRACING |
40 | bool "iwlwifi device access tracing" | |
41 | depends on IWLWIFI | |
42 | depends on EVENT_TRACING | |
43 | help | |
44 | Say Y here to trace all commands, including TX frames and IO | |
45 | accesses, sent to the device. If you say yes, iwlwifi will | |
46 | register with the ftrace framework for event tracing and dump | |
47 | all this information to the ringbuffer, you may need to | |
48 | increase the ringbuffer size. See the ftrace documentation | |
49 | for more information. | |
50 | ||
51 | When tracing is not enabled, this option still has some | |
52 | (though rather small) overhead. | |
53 | ||
54 | If unsure, say Y so we can help you better when problems | |
55 | occur. | |
56 | ||
4fc22b21 | 57 | config IWLAGN |
80bc5393 | 58 | tristate "Intel Wireless WiFi Next Gen AGN (iwlagn)" |
f82d8d97 | 59 | depends on IWLWIFI |
b481de9c | 60 | ---help--- |
c8b0e6e1 | 61 | Select to build the driver supporting the: |
b481de9c | 62 | |
4fc22b21 | 63 | Intel Wireless WiFi Link Next-Gen AGN |
b481de9c | 64 | |
c8b0e6e1 | 65 | This driver uses the kernel's mac80211 subsystem. |
b481de9c | 66 | |
c8b0e6e1 CH |
67 | In order to use this driver, you will need a microcode (uCode) |
68 | image for it. You can obtain the microcode from: | |
b481de9c | 69 | |
c8b0e6e1 | 70 | <http://intellinuxwireless.org/>. |
b481de9c | 71 | |
e7a2827c RC |
72 | The microcode is typically installed in /lib/firmware. You can |
73 | look in the hotplug script /etc/hotplug/firmware.agent to | |
74 | determine which directory FIRMWARE_DIR is set to when the script | |
75 | runs. | |
b481de9c | 76 | |
c8b0e6e1 | 77 | If you want to compile the driver as a module ( = code which can be |
7c44b6e9 | 78 | inserted in and removed from the running kernel whenever you want), |
c8b0e6e1 | 79 | say M here and read <file:Documentation/kbuild/modules.txt>. The |
4737f097 | 80 | module will be called iwlagn. |
b481de9c | 81 | |
b481de9c | 82 | |
4fc22b21 TW |
83 | config IWL4965 |
84 | bool "Intel Wireless WiFi 4965AGN" | |
85 | depends on IWLAGN | |
86 | ---help--- | |
87 | This option enables support for Intel Wireless WiFi Link 4965AGN | |
b481de9c | 88 | |
5a6a256e | 89 | config IWL5000 |
41691de3 | 90 | bool "Intel Wireless-N/Advanced-N/Ultimate-N WiFi Link" |
4fc22b21 | 91 | depends on IWLAGN |
5a6a256e | 92 | ---help--- |
41691de3 WYG |
93 | This option enables support for use with the following hardware: |
94 | Intel Wireless WiFi Link 6250AGN Adapter | |
95 | Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN) | |
96 | Intel WiFi Link 1000BGN | |
97 | Intel Wireless WiFi 5150AGN | |
98 | Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN | |
712b6cf5 | 99 | |
b481de9c | 100 | config IWL3945 |
80bc5393 | 101 | tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)" |
f82d8d97 | 102 | depends on IWLWIFI |
b481de9c ZY |
103 | ---help--- |
104 | Select to build the driver supporting the: | |
105 | ||
106 | Intel PRO/Wireless 3945ABG/BG Network Connection | |
107 | ||
108 | This driver uses the kernel's mac80211 subsystem. | |
109 | ||
b481de9c ZY |
110 | In order to use this driver, you will need a microcode (uCode) |
111 | image for it. You can obtain the microcode from: | |
112 | ||
113 | <http://intellinuxwireless.org/>. | |
114 | ||
e7a2827c RC |
115 | The microcode is typically installed in /lib/firmware. You can |
116 | look in the hotplug script /etc/hotplug/firmware.agent to | |
117 | determine which directory FIRMWARE_DIR is set to when the script | |
118 | runs. | |
b481de9c ZY |
119 | |
120 | If you want to compile the driver as a module ( = code which can be | |
7c44b6e9 | 121 | inserted in and removed from the running kernel whenever you want), |
e403149c | 122 | say M here and read <file:Documentation/kbuild/modules.txt>. The |
4737f097 | 123 | module will be called iwl3945. |