| Index: chromeos/compat-wireless/drivers/net/wireless/iwlwifi/Kconfig
|
| diff --git a/chromeos/compat-wireless/drivers/net/wireless/iwlwifi/Kconfig b/chromeos/compat-wireless/drivers/net/wireless/iwlwifi/Kconfig
|
| new file mode 100644
|
| index 0000000000000000000000000000000000000000..a51e4da1bdfc5d7149074c8adc7555d51fac0250
|
| --- /dev/null
|
| +++ b/chromeos/compat-wireless/drivers/net/wireless/iwlwifi/Kconfig
|
| @@ -0,0 +1,123 @@
|
| +config IWLWIFI
|
| + tristate "Intel Wireless Wifi"
|
| + depends on PCI && MAC80211
|
| + select FW_LOADER
|
| +
|
| +config IWLWIFI_DEBUG
|
| + bool "Enable full debugging output in iwlagn and iwl3945 drivers"
|
| + depends on IWLWIFI
|
| + ---help---
|
| + This option will enable debug tracing output for the iwlwifi drivers
|
| +
|
| + 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/class/net/wlan0/device/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/class/net/wlan0/device/debug_level
|
| +
|
| + You can find the list of debug mask values in:
|
| + drivers/net/wireless/iwlwifi/iwl-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.
|
| +
|
| +config IWLWIFI_DEBUGFS
|
| + bool "iwlagn debugfs support"
|
| + depends on IWLWIFI && MAC80211_DEBUGFS
|
| + ---help---
|
| + Enable creation of debugfs files for the iwlwifi drivers. This
|
| + is a low-impact option that allows getting insight into the
|
| + driver's state at runtime.
|
| +
|
| +config IWLWIFI_DEVICE_TRACING
|
| + bool "iwlwifi device access tracing"
|
| + depends on IWLWIFI
|
| + depends on EVENT_TRACING
|
| + help
|
| + Say Y here to trace all commands, including TX frames and IO
|
| + accesses, sent to the device. If you say yes, iwlwifi will
|
| + register with the ftrace framework for event tracing and dump
|
| + all this information to the ringbuffer, you may need to
|
| + increase the ringbuffer size. See the ftrace documentation
|
| + for more information.
|
| +
|
| + When tracing is not enabled, this option still has some
|
| + (though rather small) overhead.
|
| +
|
| + If unsure, say Y so we can help you better when problems
|
| + occur.
|
| +
|
| +config IWLAGN
|
| + tristate "Intel Wireless WiFi Next Gen AGN (iwlagn)"
|
| + depends on IWLWIFI
|
| + ---help---
|
| + Select to build the driver supporting the:
|
| +
|
| + Intel Wireless WiFi Link Next-Gen AGN
|
| +
|
| + 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/>.
|
| +
|
| + 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.
|
| +
|
| + If you want to compile the driver as a module ( = code which can be
|
| + inserted in and removed from the running kernel whenever you want),
|
| + say M here and read <file:Documentation/kbuild/modules.txt>. The
|
| + module will be called iwlagn.
|
| +
|
| +
|
| +config IWL4965
|
| + bool "Intel Wireless WiFi 4965AGN"
|
| + depends on IWLAGN
|
| + ---help---
|
| + This option enables support for Intel Wireless WiFi Link 4965AGN
|
| +
|
| +config IWL5000
|
| + bool "Intel Wireless-N/Advanced-N/Ultimate-N WiFi Link"
|
| + depends on IWLAGN
|
| + ---help---
|
| + This option enables support for use with the following hardware:
|
| + Intel Wireless WiFi Link 6250AGN Adapter
|
| + Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
|
| + Intel WiFi Link 1000BGN
|
| + Intel Wireless WiFi 5150AGN
|
| + Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
|
| +
|
| +config IWL3945
|
| + tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)"
|
| + depends on IWLWIFI
|
| + ---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/>.
|
| +
|
| + 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.
|
| +
|
| + If you want to compile the driver as a module ( = code which can be
|
| + inserted in and removed from the running kernel whenever you want),
|
| + say M here and read <file:Documentation/kbuild/modules.txt>. The
|
| + module will be called iwl3945.
|
|
|