blob: 05bd375cb845b73fbf94401ba57bfc50c59d448d [file] [log] [blame]
Stanislaw Gruszkad3175162011-11-15 11:25:42 +01001config IWLEGACY
John W. Linville4a39e782011-04-11 13:02:06 -04002 tristate
Wey-Yi Guybe663ab2011-02-21 11:27:26 -08003 select FW_LOADER
4 select NEW_LEDS
5 select LEDS_CLASS
6 select LEDS_TRIGGERS
7 select MAC80211_LEDS
8
9menu "Debugging Options"
Stanislaw Gruszkad3175162011-11-15 11:25:42 +010010 depends on IWLEGACY
Wey-Yi Guybe663ab2011-02-21 11:27:26 -080011
Stanislaw Gruszkad3175162011-11-15 11:25:42 +010012config IWLEGACY_DEBUG
13 bool "Enable full debugging output in iwlegacy (iwl 3945/4965) drivers"
14 depends on IWLEGACY
Wey-Yi Guybe663ab2011-02-21 11:27:26 -080015 ---help---
Stanislaw Gruszkad3175162011-11-15 11:25:42 +010016 This option will enable debug tracing output for the iwlegacy
Wey-Yi Guybe663ab2011-02-21 11:27:26 -080017 drivers.
18
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
21 value in
22
23 /sys/class/net/wlan0/device/debug_level
24
25 This entry will only exist if this option is enabled.
26
27 To set a value, simply echo an 8-byte hex value to the same file:
28
29 % echo 0x43fff > /sys/class/net/wlan0/device/debug_level
30
31 You can find the list of debug mask values in:
Stanislaw Gruszkaf02579e2011-08-31 14:49:56 +020032 drivers/net/wireless/iwlegacy/common.h
Wey-Yi Guybe663ab2011-02-21 11:27:26 -080033
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.
37
Stanislaw Gruszkad3175162011-11-15 11:25:42 +010038config IWLEGACY_DEBUGFS
39 bool "iwlegacy (iwl 3945/4965) debugfs support"
40 depends on IWLEGACY && MAC80211_DEBUGFS
Wey-Yi Guybe663ab2011-02-21 11:27:26 -080041 ---help---
Stanislaw Gruszkad3175162011-11-15 11:25:42 +010042 Enable creation of debugfs files for the iwlegacy drivers. This
Wey-Yi Guybe663ab2011-02-21 11:27:26 -080043 is a low-impact option that allows getting insight into the
44 driver's state at runtime.
45
Wey-Yi Guybe663ab2011-02-21 11:27:26 -080046endmenu
47
48config IWL4965
49 tristate "Intel Wireless WiFi 4965AGN (iwl4965)"
John W. Linville4a39e782011-04-11 13:02:06 -040050 depends on PCI && MAC80211
Stanislaw Gruszkad3175162011-11-15 11:25:42 +010051 select IWLEGACY
Wey-Yi Guybe663ab2011-02-21 11:27:26 -080052 ---help---
53 This option enables support for
54
55 Select to build the driver supporting the:
56
57 Intel Wireless WiFi Link 4965AGN
58
59 This driver uses the kernel's mac80211 subsystem.
60
61 In order to use this driver, you will need a microcode (uCode)
62 image for it. You can obtain the microcode from:
63
64 <http://intellinuxwireless.org/>.
65
66 The microcode is typically installed in /lib/firmware. You can
67 look in the hotplug script /etc/hotplug/firmware.agent to
68 determine which directory FIRMWARE_DIR is set to when the script
69 runs.
70
71 If you want to compile the driver as a module ( = code which can be
72 inserted in and removed from the running kernel whenever you want),
73 say M here and read <file:Documentation/kbuild/modules.txt>. The
74 module will be called iwl4965.
75
76config IWL3945
77 tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)"
John W. Linville4a39e782011-04-11 13:02:06 -040078 depends on PCI && MAC80211
Stanislaw Gruszkad3175162011-11-15 11:25:42 +010079 select IWLEGACY
Wey-Yi Guybe663ab2011-02-21 11:27:26 -080080 ---help---
81 Select to build the driver supporting the:
82
83 Intel PRO/Wireless 3945ABG/BG Network Connection
84
85 This driver uses the kernel's mac80211 subsystem.
86
87 In order to use this driver, you will need a microcode (uCode)
88 image for it. You can obtain the microcode from:
89
90 <http://intellinuxwireless.org/>.
91
92 The microcode is typically installed in /lib/firmware. You can
93 look in the hotplug script /etc/hotplug/firmware.agent to
94 determine which directory FIRMWARE_DIR is set to when the script
95 runs.
96
97 If you want to compile the driver as a module ( = code which can be
98 inserted in and removed from the running kernel whenever you want),
99 say M here and read <file:Documentation/kbuild/modules.txt>. The
100 module will be called iwl3945.