2008-03-07 02:40:19 +08:00
|
|
|
config IWLCORE
|
|
|
|
tristate "Intel Wireless Wifi Core"
|
|
|
|
depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL
|
|
|
|
|
2008-03-26 07:33:36 +08:00
|
|
|
config IWLWIFI_LEDS
|
2008-04-03 00:10:04 +08:00
|
|
|
bool
|
|
|
|
default n
|
2008-03-26 07:33:36 +08:00
|
|
|
|
2008-04-15 12:16:12 +08:00
|
|
|
config IWLWIFI_RFKILL
|
2008-03-29 07:21:06 +08:00
|
|
|
boolean "IWLWIFI RF kill support"
|
|
|
|
depends on IWLCORE
|
|
|
|
select RFKILL
|
|
|
|
select RFKILL_INPUT
|
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
config IWL4965
|
|
|
|
tristate "Intel Wireless WiFi 4965AGN"
|
2008-01-28 08:41:47 +08:00
|
|
|
depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL
|
2007-09-26 08:54:57 +08:00
|
|
|
select FW_LOADER
|
2008-03-07 02:40:19 +08:00
|
|
|
select IWLCORE
|
2007-09-26 08:54:57 +08:00
|
|
|
---help---
|
2007-10-25 17:15:51 +08:00
|
|
|
Select to build the driver supporting the:
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
Intel Wireless WiFi Link 4965AGN
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
This driver uses the kernel's mac80211 subsystem.
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
In order to use this driver, you will need a microcode (uCode)
|
|
|
|
image for it. You can obtain the microcode from:
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
<http://intellinuxwireless.org/>.
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2008-01-15 09:46:24 +08:00
|
|
|
The microcode is typically installed in /lib/firmware. You can
|
|
|
|
look in the hotplug script /etc/hotplug/firmware.agent to
|
|
|
|
determine which directory FIRMWARE_DIR is set to when the script
|
|
|
|
runs.
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
If you want to compile the driver as a module ( = code which can be
|
2008-03-14 02:13:24 +08:00
|
|
|
inserted in and removed from the running kernel whenever you want),
|
2007-10-25 17:15:51 +08:00
|
|
|
say M here and read <file:Documentation/kbuild/modules.txt>. The
|
|
|
|
module will be called iwl4965.ko.
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-11-26 22:14:35 +08:00
|
|
|
config IWL4965_HT
|
|
|
|
bool "Enable 802.11n HT features in iwl4965 driver"
|
|
|
|
depends on EXPERIMENTAL
|
2008-02-07 03:20:39 +08:00
|
|
|
depends on IWL4965
|
2007-11-26 22:14:35 +08:00
|
|
|
---help---
|
|
|
|
This option enables IEEE 802.11n High Throughput features
|
|
|
|
for the iwl4965 driver.
|
|
|
|
|
2008-03-26 07:33:36 +08:00
|
|
|
config IWL4965_LEDS
|
|
|
|
bool "Enable LEDS features in iwl4965 driver"
|
2008-04-23 18:34:31 +08:00
|
|
|
depends on IWL4965
|
|
|
|
select MAC80211_LEDS
|
|
|
|
select LEDS_CLASS
|
2008-04-03 00:10:04 +08:00
|
|
|
select IWLWIFI_LEDS
|
2008-03-26 07:33:36 +08:00
|
|
|
---help---
|
|
|
|
This option enables LEDS for the iwlwifi drivers
|
|
|
|
|
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
config IWL4965_SPECTRUM_MEASUREMENT
|
2008-01-05 14:53:11 +08:00
|
|
|
bool "Enable Spectrum Measurement in iwl4965 driver"
|
2007-10-25 17:15:51 +08:00
|
|
|
depends on IWL4965
|
2007-09-26 08:54:57 +08:00
|
|
|
---help---
|
2007-10-25 17:15:51 +08:00
|
|
|
This option will enable spectrum measurement for the iwl4965 driver.
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
config IWL4965_SENSITIVITY
|
|
|
|
bool "Enable Sensitivity Calibration in iwl4965 driver"
|
|
|
|
depends on IWL4965
|
2007-09-26 08:54:57 +08:00
|
|
|
---help---
|
2007-10-25 17:15:51 +08:00
|
|
|
This option will enable sensitivity calibration for the iwl4965
|
|
|
|
driver.
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2008-03-13 07:58:49 +08:00
|
|
|
config IWLWIFI_DEBUG
|
2007-10-25 17:15:51 +08:00
|
|
|
bool "Enable full debugging output in iwl4965 driver"
|
|
|
|
depends on IWL4965
|
2007-09-26 08:54:57 +08:00
|
|
|
---help---
|
2007-10-25 17:15:51 +08:00
|
|
|
This option will enable debug tracing output for the iwl4965
|
|
|
|
driver.
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
This will result in the kernel module being ~100k larger. You can
|
|
|
|
control which debug output is sent to the kernel log by setting the
|
|
|
|
value in
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
/sys/bus/pci/drivers/${DRIVER}/debug_level
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
This entry will only exist if this option is enabled.
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
To set a value, simply echo an 8-byte hex value to the same file:
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
% echo 0x43fff > /sys/bus/pci/drivers/${DRIVER}/debug_level
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
You can find the list of debug mask values in:
|
|
|
|
drivers/net/wireless/iwlwifi/iwl-4965-debug.h
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
If this is your first time using this driver, you should say Y here
|
|
|
|
as the debug information can assist others in helping you resolve
|
|
|
|
any problems you may encounter.
|
2007-09-26 08:54:57 +08:00
|
|
|
|
2008-03-13 07:58:52 +08:00
|
|
|
config IWLWIFI_DEBUGFS
|
|
|
|
bool "Iwlwifi debugfs support"
|
|
|
|
depends on IWLCORE && IWLWIFI_DEBUG && MAC80211_DEBUGFS
|
|
|
|
---help---
|
|
|
|
Enable creation of debugfs files for the iwlwifi drivers.
|
|
|
|
|
2007-09-26 08:54:57 +08:00
|
|
|
config IWL3945
|
|
|
|
tristate "Intel PRO/Wireless 3945ABG/BG Network Connection"
|
2008-01-28 08:41:47 +08:00
|
|
|
depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL
|
2007-10-25 17:15:51 +08:00
|
|
|
select FW_LOADER
|
2007-09-26 08:54:57 +08:00
|
|
|
---help---
|
|
|
|
Select to build the driver supporting the:
|
|
|
|
|
|
|
|
Intel PRO/Wireless 3945ABG/BG Network Connection
|
|
|
|
|
|
|
|
This driver uses the kernel's mac80211 subsystem.
|
|
|
|
|
|
|
|
In order to use this driver, you will need a microcode (uCode)
|
|
|
|
image for it. You can obtain the microcode from:
|
|
|
|
|
|
|
|
<http://intellinuxwireless.org/>.
|
|
|
|
|
2008-01-15 09:46:24 +08:00
|
|
|
The microcode is typically installed in /lib/firmware. You can
|
|
|
|
look in the hotplug script /etc/hotplug/firmware.agent to
|
|
|
|
determine which directory FIRMWARE_DIR is set to when the script
|
|
|
|
runs.
|
2007-09-26 08:54:57 +08:00
|
|
|
|
|
|
|
If you want to compile the driver as a module ( = code which can be
|
2008-03-14 02:13:24 +08:00
|
|
|
inserted in and removed from the running kernel whenever you want),
|
2007-10-31 04:37:19 +08:00
|
|
|
say M here and read <file:Documentation/kbuild/modules.txt>. The
|
|
|
|
module will be called iwl3945.ko.
|
2007-10-25 17:15:51 +08:00
|
|
|
|
|
|
|
config IWL3945_SPECTRUM_MEASUREMENT
|
|
|
|
bool "Enable Spectrum Measurement in iwl3945 drivers"
|
|
|
|
depends on IWL3945
|
|
|
|
---help---
|
|
|
|
This option will enable spectrum measurement for the iwl3945 driver.
|
|
|
|
|
2008-03-26 07:33:36 +08:00
|
|
|
config IWL3945_LEDS
|
|
|
|
bool "Enable LEDS features in iwl3945 driver"
|
2008-04-23 18:34:31 +08:00
|
|
|
depends on IWL3945
|
|
|
|
select MAC80211_LEDS
|
|
|
|
select LEDS_CLASS
|
2008-03-26 07:33:36 +08:00
|
|
|
---help---
|
|
|
|
This option enables LEDS for the iwl3945 driver.
|
|
|
|
|
2007-10-25 17:15:51 +08:00
|
|
|
config IWL3945_DEBUG
|
|
|
|
bool "Enable full debugging output in iwl3945 driver"
|
|
|
|
depends on IWL3945
|
|
|
|
---help---
|
|
|
|
This option will enable debug tracing output for the iwl3945
|
|
|
|
driver.
|
|
|
|
|
|
|
|
This will result in the kernel module being ~100k larger. You can
|
|
|
|
control which debug output is sent to the kernel log by setting the
|
|
|
|
value in
|
|
|
|
|
|
|
|
/sys/bus/pci/drivers/${DRIVER}/debug_level
|
|
|
|
|
|
|
|
This entry will only exist if this option is enabled.
|
|
|
|
|
|
|
|
To set a value, simply echo an 8-byte hex value to the same file:
|
|
|
|
|
|
|
|
% echo 0x43fff > /sys/bus/pci/drivers/${DRIVER}/debug_level
|
|
|
|
|
|
|
|
You can find the list of debug mask values in:
|
|
|
|
drivers/net/wireless/iwlwifi/iwl-3945-debug.h
|
|
|
|
|
|
|
|
If this is your first time using this driver, you should say Y here
|
|
|
|
as the debug information can assist others in helping you resolve
|
|
|
|
any problems you may encounter.
|
|
|
|
|