blob: 62fb89d8231821637de3feb9f46862aa5b1da410 [file] [log] [blame]
Jason Riedy358c1292008-04-27 15:38:30 -07001config IWLWIFI
Adrian Bunk1da5ea12008-05-06 00:04:47 -07002 tristate
Jason Riedy358c1292008-04-27 15:38:30 -07003
Tomas Winklerdf48c322008-03-06 10:40:19 -08004config IWLCORE
5 tristate "Intel Wireless Wifi Core"
6 depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL
Jason Riedy358c1292008-04-27 15:38:30 -07007 select IWLWIFI
Adrian Bunk3a8209d2008-04-29 22:29:59 -07008 select MAC80211_LEDS if IWLWIFI_LEDS
9 select LEDS_CLASS if IWLWIFI_LEDS
10 select RFKILL if IWLWIFI_RFKILL
11 select RFKILL_INPUT if IWLWIFI_RFKILL
Tomas Winklerdf48c322008-03-06 10:40:19 -080012
Mohamed Abbasab53d8a2008-03-25 16:33:36 -070013config IWLWIFI_LEDS
John W. Linville53f36d72008-04-02 12:10:04 -040014 bool
15 default n
Mohamed Abbasab53d8a2008-03-25 16:33:36 -070016
Reinette Chatreeadd3c42008-04-14 21:16:12 -070017config IWLWIFI_RFKILL
Mohamed Abbasad97edd22008-03-28 16:21:06 -070018 boolean "IWLWIFI RF kill support"
19 depends on IWLCORE
Mohamed Abbasad97edd22008-03-28 16:21:06 -070020
Zhu Yib481de92007-09-25 17:54:57 -070021config IWL4965
22 tristate "Intel Wireless WiFi 4965AGN"
Christoph Hellwigbb8c0932008-01-27 16:41:47 -080023 depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +080024 select FW_LOADER
Tomas Winklerdf48c322008-03-06 10:40:19 -080025 select IWLCORE
Zhu Yib481de92007-09-25 17:54:57 -070026 ---help---
27 Select to build the driver supporting the:
28
29 Intel Wireless WiFi Link 4965AGN
30
31 This driver uses the kernel's mac80211 subsystem.
32
Zhu Yib481de92007-09-25 17:54:57 -070033 In order to use this driver, you will need a microcode (uCode)
34 image for it. You can obtain the microcode from:
35
36 <http://intellinuxwireless.org/>.
37
Reinette Chatree7a28272008-01-14 17:46:24 -080038 The microcode is typically installed in /lib/firmware. You can
39 look in the hotplug script /etc/hotplug/firmware.agent to
40 determine which directory FIRMWARE_DIR is set to when the script
41 runs.
Zhu Yib481de92007-09-25 17:54:57 -070042
43 If you want to compile the driver as a module ( = code which can be
Pascal Terjan7c44b6e2008-03-13 19:13:24 +010044 inserted in and removed from the running kernel whenever you want),
Dirk Hohndele4031492007-10-30 13:37:19 -070045 say M here and read <file:Documentation/kbuild/modules.txt>. The
46 module will be called iwl4965.ko.
Zhu Yib481de92007-09-25 17:54:57 -070047
Ron Rindjunsky923effd2007-11-26 16:14:35 +020048config IWL4965_HT
49 bool "Enable 802.11n HT features in iwl4965 driver"
50 depends on EXPERIMENTAL
Ron Rindjunsky292ae172008-02-06 11:20:39 -080051 depends on IWL4965
Ron Rindjunsky923effd2007-11-26 16:14:35 +020052 ---help---
53 This option enables IEEE 802.11n High Throughput features
54 for the iwl4965 driver.
55
Mohamed Abbasab53d8a2008-03-25 16:33:36 -070056config IWL4965_LEDS
57 bool "Enable LEDS features in iwl4965 driver"
David S. Millere82404a2008-04-23 03:34:31 -070058 depends on IWL4965
John W. Linville53f36d72008-04-02 12:10:04 -040059 select IWLWIFI_LEDS
Mohamed Abbasab53d8a2008-03-25 16:33:36 -070060 ---help---
61 This option enables LEDS for the iwlwifi drivers
62
63
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +080064config IWL4965_SPECTRUM_MEASUREMENT
Zhu Yi66c6b132008-01-04 22:53:11 -080065 bool "Enable Spectrum Measurement in iwl4965 driver"
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +080066 depends on IWL4965
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +080067 ---help---
68 This option will enable spectrum measurement for the iwl4965 driver.
69
70config IWL4965_SENSITIVITY
71 bool "Enable Sensitivity Calibration in iwl4965 driver"
72 depends on IWL4965
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +080073 ---help---
74 This option will enable sensitivity calibration for the iwl4965
75 driver.
76
Tomas Winkler0a6857e2008-03-12 16:58:49 -070077config IWLWIFI_DEBUG
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +080078 bool "Enable full debugging output in iwl4965 driver"
79 depends on IWL4965
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +080080 ---help---
81 This option will enable debug tracing output for the iwl4965
82 driver.
83
84 This will result in the kernel module being ~100k larger. You can
85 control which debug output is sent to the kernel log by setting the
86 value in
87
88 /sys/bus/pci/drivers/${DRIVER}/debug_level
89
90 This entry will only exist if this option is enabled.
91
92 To set a value, simply echo an 8-byte hex value to the same file:
93
94 % echo 0x43fff > /sys/bus/pci/drivers/${DRIVER}/debug_level
95
96 You can find the list of debug mask values in:
97 drivers/net/wireless/iwlwifi/iwl-4965-debug.h
98
99 If this is your first time using this driver, you should say Y here
100 as the debug information can assist others in helping you resolve
101 any problems you may encounter.
102
Tomas Winkler712b6cf2008-03-12 16:58:52 -0700103config IWLWIFI_DEBUGFS
104 bool "Iwlwifi debugfs support"
105 depends on IWLCORE && IWLWIFI_DEBUG && MAC80211_DEBUGFS
106 ---help---
107 Enable creation of debugfs files for the iwlwifi drivers.
108
Zhu Yib481de92007-09-25 17:54:57 -0700109config IWL3945
110 tristate "Intel PRO/Wireless 3945ABG/BG Network Connection"
Christoph Hellwigbb8c0932008-01-27 16:41:47 -0800111 depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +0800112 select FW_LOADER
Jason Riedy358c1292008-04-27 15:38:30 -0700113 select IWLWIFI
Adrian Bunk3a8209d2008-04-29 22:29:59 -0700114 select MAC80211_LEDS if IWL3945_LEDS
115 select LEDS_CLASS if IWL3945_LEDS
Zhu Yib481de92007-09-25 17:54:57 -0700116 ---help---
117 Select to build the driver supporting the:
118
119 Intel PRO/Wireless 3945ABG/BG Network Connection
120
121 This driver uses the kernel's mac80211 subsystem.
122
Zhu Yib481de92007-09-25 17:54:57 -0700123 In order to use this driver, you will need a microcode (uCode)
124 image for it. You can obtain the microcode from:
125
126 <http://intellinuxwireless.org/>.
127
Reinette Chatree7a28272008-01-14 17:46:24 -0800128 The microcode is typically installed in /lib/firmware. You can
129 look in the hotplug script /etc/hotplug/firmware.agent to
130 determine which directory FIRMWARE_DIR is set to when the script
131 runs.
Zhu Yib481de92007-09-25 17:54:57 -0700132
133 If you want to compile the driver as a module ( = code which can be
Pascal Terjan7c44b6e2008-03-13 19:13:24 +0100134 inserted in and removed from the running kernel whenever you want),
Dirk Hohndele4031492007-10-30 13:37:19 -0700135 say M here and read <file:Documentation/kbuild/modules.txt>. The
136 module will be called iwl3945.ko.
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +0800137
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +0800138config IWL3945_SPECTRUM_MEASUREMENT
139 bool "Enable Spectrum Measurement in iwl3945 drivers"
140 depends on IWL3945
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +0800141 ---help---
142 This option will enable spectrum measurement for the iwl3945 driver.
143
Mohamed Abbasab53d8a2008-03-25 16:33:36 -0700144config IWL3945_LEDS
145 bool "Enable LEDS features in iwl3945 driver"
David S. Millere82404a2008-04-23 03:34:31 -0700146 depends on IWL3945
Mohamed Abbasab53d8a2008-03-25 16:33:36 -0700147 ---help---
148 This option enables LEDS for the iwl3945 driver.
149
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +0800150config IWL3945_DEBUG
151 bool "Enable full debugging output in iwl3945 driver"
152 depends on IWL3945
Christoph Hellwigc8b0e6e2007-10-25 17:15:51 +0800153 ---help---
154 This option will enable debug tracing output for the iwl3945
155 driver.
156
157 This will result in the kernel module being ~100k larger. You can
158 control which debug output is sent to the kernel log by setting the
159 value in
160
161 /sys/bus/pci/drivers/${DRIVER}/debug_level
162
163 This entry will only exist if this option is enabled.
164
165 To set a value, simply echo an 8-byte hex value to the same file:
166
167 % echo 0x43fff > /sys/bus/pci/drivers/${DRIVER}/debug_level
168
169 You can find the list of debug mask values in:
170 drivers/net/wireless/iwlwifi/iwl-3945-debug.h
171
172 If this is your first time using this driver, you should say Y here
173 as the debug information can assist others in helping you resolve
174 any problems you may encounter.
175