Commit | Line | Data |
---|---|---|
be663ab6 WYG |
1 | config IWLWIFI_LEGACY |
2 | tristate "Intel Wireless Wifi legacy devices" | |
3 | depends on PCI && MAC80211 | |
4 | select FW_LOADER | |
5 | select NEW_LEDS | |
6 | select LEDS_CLASS | |
7 | select LEDS_TRIGGERS | |
8 | select MAC80211_LEDS | |
9 | ||
10 | menu "Debugging Options" | |
11 | depends on IWLWIFI_LEGACY | |
12 | ||
13 | config IWLWIFI_LEGACY_DEBUG | |
14 | bool "Enable full debugging output in 4965 and 3945 drivers" | |
15 | depends on IWLWIFI_LEGACY | |
16 | ---help--- | |
17 | This option will enable debug tracing output for the iwlwifilegacy | |
18 | drivers. | |
19 | ||
20 | This will result in the kernel module being ~100k larger. You can | |
21 | control which debug output is sent to the kernel log by setting the | |
22 | value in | |
23 | ||
24 | /sys/class/net/wlan0/device/debug_level | |
25 | ||
26 | This entry will only exist if this option is enabled. | |
27 | ||
28 | To set a value, simply echo an 8-byte hex value to the same file: | |
29 | ||
30 | % echo 0x43fff > /sys/class/net/wlan0/device/debug_level | |
31 | ||
32 | You can find the list of debug mask values in: | |
33 | drivers/net/wireless/iwlwifilegacy/iwl-debug.h | |
34 | ||
35 | If this is your first time using this driver, you should say Y here | |
36 | as the debug information can assist others in helping you resolve | |
37 | any problems you may encounter. | |
38 | ||
39 | config IWLWIFI_LEGACY_DEBUGFS | |
40 | bool "4965 and 3945 debugfs support" | |
41 | depends on IWLWIFI_LEGACY && MAC80211_DEBUGFS | |
42 | ---help--- | |
43 | Enable creation of debugfs files for the iwlwifilegacy drivers. This | |
44 | is a low-impact option that allows getting insight into the | |
45 | driver's state at runtime. | |
46 | ||
47 | config IWLWIFI_LEGACY_DEVICE_TRACING | |
48 | bool "iwlwifilegacy legacy device access tracing" | |
49 | depends on IWLWIFI_LEGACY | |
50 | depends on EVENT_TRACING | |
51 | help | |
52 | Say Y here to trace all commands, including TX frames and IO | |
53 | accesses, sent to the device. If you say yes, iwlwifilegacy will | |
54 | register with the ftrace framework for event tracing and dump | |
55 | all this information to the ringbuffer, you may need to | |
56 | increase the ringbuffer size. See the ftrace documentation | |
57 | for more information. | |
58 | ||
59 | When tracing is not enabled, this option still has some | |
60 | (though rather small) overhead. | |
61 | ||
62 | If unsure, say Y so we can help you better when problems | |
63 | occur. | |
64 | endmenu | |
65 | ||
66 | config IWL4965 | |
67 | tristate "Intel Wireless WiFi 4965AGN (iwl4965)" | |
68 | depends on IWLWIFI_LEGACY | |
69 | ---help--- | |
70 | This option enables support for | |
71 | ||
72 | Select to build the driver supporting the: | |
73 | ||
74 | Intel Wireless WiFi Link 4965AGN | |
75 | ||
76 | This driver uses the kernel's mac80211 subsystem. | |
77 | ||
78 | In order to use this driver, you will need a microcode (uCode) | |
79 | image for it. You can obtain the microcode from: | |
80 | ||
81 | <http://intellinuxwireless.org/>. | |
82 | ||
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 | |
86 | runs. | |
87 | ||
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. | |
92 | ||
93 | config IWL3945 | |
94 | tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)" | |
95 | depends on IWLWIFI_LEGACY | |
96 | ---help--- | |
97 | Select to build the driver supporting the: | |
98 | ||
99 | Intel PRO/Wireless 3945ABG/BG Network Connection | |
100 | ||
101 | This driver uses the kernel's mac80211 subsystem. | |
102 | ||
103 | In order to use this driver, you will need a microcode (uCode) | |
104 | image for it. You can obtain the microcode from: | |
105 | ||
106 | <http://intellinuxwireless.org/>. | |
107 | ||
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 | |
111 | runs. | |
112 | ||
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. |