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         select NEW_LEDS
   6         select LEDS_CLASS
   7         select LEDS_TRIGGERS
   8         select MAC80211_LEDS
   9         select IWLDVM
  10         ---help---
  11           Select to build the driver supporting the:
  12
  13           Intel Wireless WiFi Link Next-Gen AGN
  14
  15           This option enables support for use with the following hardware:
  16                 Intel Wireless WiFi Link 6250AGN Adapter
  17                 Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
  18                 Intel WiFi Link 1000BGN
  19                 Intel Wireless WiFi 5150AGN
  20                 Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
  21                 Intel 6005 Series Wi-Fi Adapters
  22                 Intel 6030 Series Wi-Fi Adapters
  23                 Intel Wireless WiFi Link 6150BGN 2 Adapter
  24                 Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN)
  25                 Intel 2000 Series Wi-Fi Adapters
  26
  27
  28           This driver uses the kernel's mac80211 subsystem.
  29
  30           In order to use this driver, you will need a microcode (uCode)
  31           image for it. You can obtain the microcode from:
  32
  33                   <http://intellinuxwireless.org/>.
  34
  35           The microcode is typically installed in /lib/firmware. You can
  36           look in the hotplug script /etc/hotplug/firmware.agent to
  37           determine which directory FIRMWARE_DIR is set to when the script
  38           runs.
  39
  40           If you want to compile the driver as a module ( = code which can be
  41           inserted in and removed from the running kernel whenever you want),
  42           say M here and read <file:Documentation/kbuild/modules.txt>.  The
  43           module will be called iwlwifi.
  44
  45 config IWLDVM
  46         tristate "Intel Wireless WiFi"
  47         depends on IWLWIFI
  48
  49 menu "Debugging Options"
  50         depends on IWLWIFI
  51
  52 config IWLWIFI_DEBUG
  53         bool "Enable full debugging output in the iwlwifi driver"
  54         depends on IWLWIFI
  55         ---help---
  56           This option will enable debug tracing output for the iwlwifi drivers
  57
  58           This will result in the kernel module being ~100k larger.  You can
  59           control which debug output is sent to the kernel log by setting the
  60           value in
  61
  62                 /sys/module/iwlwifi/parameters/debug
  63
  64           This entry will only exist if this option is enabled.
  65
  66           To set a value, simply echo an 8-byte hex value to the same file:
  67
  68                   % echo 0x43fff > /sys/module/iwlwifi/parameters/debug
  69
  70           You can find the list of debug mask values in:
  71                   drivers/net/wireless/iwlwifi/iwl-debug.h
  72
  73           If this is your first time using this driver, you should say Y here
  74           as the debug information can assist others in helping you resolve
  75           any problems you may encounter.
  76
  77 config IWLWIFI_DEBUGFS
  78         bool "iwlwifi debugfs support"
  79         depends on IWLWIFI && MAC80211_DEBUGFS
  80         ---help---
  81           Enable creation of debugfs files for the iwlwifi drivers. This
  82           is a low-impact option that allows getting insight into the
  83           driver's state at runtime.
  84
  85 config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE
  86         bool "Experimental uCode support"
  87         depends on IWLWIFI && IWLWIFI_DEBUG
  88         ---help---
  89           Enable use of experimental ucode for testing and debugging.
  90
  91 config IWLWIFI_DEVICE_TRACING
  92         bool "iwlwifi device access tracing"
  93         depends on IWLWIFI
  94         depends on EVENT_TRACING
  95         help
  96           Say Y here to trace all commands, including TX frames and IO
  97           accesses, sent to the device. If you say yes, iwlwifi will
  98           register with the ftrace framework for event tracing and dump
  99           all this information to the ringbuffer, you may need to
 100           increase the ringbuffer size. See the ftrace documentation
 101           for more information.
 102
 103           When tracing is not enabled, this option still has some
 104           (though rather small) overhead.
 105
 106           If unsure, say Y so we can help you better when problems
 107           occur.
 108 endmenu
 109
 110 config IWLWIFI_DEVICE_TESTMODE
 111         def_bool y
 112         depends on IWLWIFI
 113         depends on NL80211_TESTMODE
 114         help
 115           This option enables the testmode support for iwlwifi device through
 116           NL80211_TESTMODE. This provide the capabilities of enable user space
 117           validation applications to interacts with the device through the
 118           generic netlink message via NL80211_TESTMODE channel.
 119
 120 config IWLWIFI_P2P
 121         def_bool y
 122         bool "iwlwifi experimental P2P support"
 123         depends on IWLWIFI
 124         help
 125           This option enables experimental P2P support for some devices
 126           based on microcode support. Since P2P support is still under
 127           development, this option may even enable it for some devices
 128           now that turn out to not support it in the future due to
 129           microcode restrictions.
 130
 131           To determine if your microcode supports the experimental P2P
 132           offered by this option, check if the driver advertises AP
 133           support when it is loaded.
 134
 135           Say Y only if you want to experiment with P2P.