Kconfig 5.1 KB

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