Kconfig 4.8 KB

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