Version:  2.0.40 2.2.26 2.4.37 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1

Linux/drivers/net/wireless/iwlwifi/Kconfig

  1 config IWLWIFI
  2         tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi) "
  3         depends on PCI && MAC80211 && HAS_IOMEM
  4         select FW_LOADER
  5         ---help---
  6           Select to build the driver supporting the:
  7 
  8           Intel Wireless WiFi Link Next-Gen AGN
  9 
 10           This option enables support for use with the following hardware:
 11                 Intel Wireless WiFi Link 6250AGN Adapter
 12                 Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
 13                 Intel WiFi Link 1000BGN
 14                 Intel Wireless WiFi 5150AGN
 15                 Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
 16                 Intel 6005 Series Wi-Fi Adapters
 17                 Intel 6030 Series Wi-Fi Adapters
 18                 Intel Wireless WiFi Link 6150BGN 2 Adapter
 19                 Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
 20                 Intel 2000 Series Wi-Fi Adapters
 21                 Intel 7260 Wi-Fi Adapter
 22                 Intel 3160 Wi-Fi Adapter
 23                 Intel 7265 Wi-Fi Adapter
 24                 Intel 3165 Wi-Fi Adapter
 25 
 26 
 27           This driver uses the kernel's mac80211 subsystem.
 28 
 29           In order to use this driver, you will need a firmware
 30           image for it. You can obtain the microcode from:
 31 
 32                   <http://wireless.kernel.org/en/users/Drivers/iwlwifi>.
 33 
 34           The firmware is typically installed in /lib/firmware. You can
 35           look in the hotplug script /etc/hotplug/firmware.agent to
 36           determine which directory FIRMWARE_DIR is set to when the script
 37           runs.
 38 
 39           If you want to compile the driver as a module ( = code which can be
 40           inserted in and removed from the running kernel whenever you want),
 41           say M here and read <file:Documentation/kbuild/modules.txt>.  The
 42           module will be called iwlwifi.
 43 
 44 if IWLWIFI
 45 
 46 config IWLWIFI_LEDS
 47         bool
 48         depends on LEDS_CLASS=y || LEDS_CLASS=IWLWIFI
 49         select LEDS_TRIGGERS
 50         select MAC80211_LEDS
 51         default y
 52 
 53 config IWLDVM
 54         tristate "Intel Wireless WiFi DVM Firmware support"
 55         default IWLWIFI
 56         help
 57           This is the driver that supports the DVM firmware which is
 58           used by most existing devices (with the exception of 7260
 59           and 3160).
 60 
 61 config IWLMVM
 62         tristate "Intel Wireless WiFi MVM Firmware support"
 63         select WANT_DEV_COREDUMP
 64         help
 65           This is the driver that supports the MVM firmware which is
 66           currently only available for 7260 and 3160 devices.
 67 
 68 # don't call it _MODULE -- will confuse Kconfig/fixdep/...
 69 config IWLWIFI_OPMODE_MODULAR
 70         bool
 71         default y if IWLDVM=m
 72         default y if IWLMVM=m
 73 
 74 comment "WARNING: iwlwifi is useless without IWLDVM or IWLMVM"
 75         depends on IWLDVM=n && IWLMVM=n
 76 
 77 config IWLWIFI_BCAST_FILTERING
 78         bool "Enable broadcast filtering"
 79         depends on IWLMVM
 80         help
 81           Say Y here to enable default bcast filtering configuration.
 82 
 83           Enabling broadcast filtering will drop any incoming wireless
 84           broadcast frames, except some very specific predefined
 85           patterns (e.g. incoming arp requests).
 86 
 87           If unsure, don't enable this option, as some programs might
 88           expect incoming broadcasts for their normal operations.
 89 
 90 config IWLWIFI_UAPSD
 91         bool "enable U-APSD by default"
 92         depends on IWLMVM
 93         help
 94           Say Y here to enable U-APSD by default. This may cause
 95           interoperability problems with some APs, manifesting in lower than
 96           expected throughput due to those APs not enabling aggregation
 97 
 98           If unsure, say N.
 99 
100 menu "Debugging Options"
101 
102 config IWLWIFI_DEBUG
103         bool "Enable full debugging output in the iwlwifi driver"
104         ---help---
105           This option will enable debug tracing output for the iwlwifi drivers
106 
107           This will result in the kernel module being ~100k larger.  You can
108           control which debug output is sent to the kernel log by setting the
109           value in
110 
111                 /sys/module/iwlwifi/parameters/debug
112 
113           This entry will only exist if this option is enabled.
114 
115           To set a value, simply echo an 8-byte hex value to the same file:
116 
117                   % echo 0x43fff > /sys/module/iwlwifi/parameters/debug
118 
119           You can find the list of debug mask values in:
120                   drivers/net/wireless/iwlwifi/iwl-debug.h
121 
122           If this is your first time using this driver, you should say Y here
123           as the debug information can assist others in helping you resolve
124           any problems you may encounter.
125 
126 config IWLWIFI_DEBUGFS
127         bool "iwlwifi debugfs support"
128         depends on MAC80211_DEBUGFS
129         ---help---
130           Enable creation of debugfs files for the iwlwifi drivers. This
131           is a low-impact option that allows getting insight into the
132           driver's state at runtime.
133 
134 config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE
135         bool "Experimental uCode support"
136         depends on IWLWIFI_DEBUG
137         ---help---
138           Enable use of experimental ucode for testing and debugging.
139 
140 config IWLWIFI_DEVICE_TRACING
141         bool "iwlwifi device access tracing"
142         depends on EVENT_TRACING
143         help
144           Say Y here to trace all commands, including TX frames and IO
145           accesses, sent to the device. If you say yes, iwlwifi will
146           register with the ftrace framework for event tracing and dump
147           all this information to the ringbuffer, you may need to
148           increase the ringbuffer size. See the ftrace documentation
149           for more information.
150 
151           When tracing is not enabled, this option still has some
152           (though rather small) overhead.
153 
154           If unsure, say Y so we can help you better when problems
155           occur.
156 endmenu
157 
158 endif

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us