Kconfig 5.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175
  1. config IWLWIFI
  2. tristate
  3. config IWLCORE
  4. tristate "Intel Wireless Wifi Core"
  5. depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL
  6. select IWLWIFI
  7. select MAC80211_LEDS if IWLWIFI_LEDS
  8. select LEDS_CLASS if IWLWIFI_LEDS
  9. select RFKILL if IWLWIFI_RFKILL
  10. config IWLWIFI_LEDS
  11. bool
  12. default n
  13. config IWLWIFI_RFKILL
  14. boolean "Iwlwifi RF kill support"
  15. depends on IWLCORE
  16. config IWLWIFI_DEBUG
  17. bool "Enable full debugging output in iwlagn driver"
  18. depends on IWLCORE
  19. ---help---
  20. This option will enable debug tracing output for the iwlwifi drivers
  21. This will result in the kernel module being ~100k larger. You can
  22. control which debug output is sent to the kernel log by setting the
  23. value in
  24. /sys/class/net/wlan0/device/debug_level
  25. This entry will only exist if this option is enabled.
  26. To set a value, simply echo an 8-byte hex value to the same file:
  27. % echo 0x43fff > /sys/class/net/wlan0/device/debug_level
  28. You can find the list of debug mask values in:
  29. drivers/net/wireless/iwlwifi/iwl-debug.h
  30. If this is your first time using this driver, you should say Y here
  31. as the debug information can assist others in helping you resolve
  32. any problems you may encounter.
  33. config IWLWIFI_DEBUGFS
  34. bool "Iwlwifi debugfs support"
  35. depends on IWLCORE && IWLWIFI_DEBUG && MAC80211_DEBUGFS
  36. ---help---
  37. Enable creation of debugfs files for the iwlwifi drivers.
  38. config IWLAGN
  39. tristate "Intel Wireless WiFi Next Gen AGN"
  40. depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL
  41. select FW_LOADER
  42. select IWLCORE
  43. ---help---
  44. Select to build the driver supporting the:
  45. Intel Wireless WiFi Link Next-Gen AGN
  46. This driver uses the kernel's mac80211 subsystem.
  47. In order to use this driver, you will need a microcode (uCode)
  48. image for it. You can obtain the microcode from:
  49. <http://intellinuxwireless.org/>.
  50. The microcode is typically installed in /lib/firmware. You can
  51. look in the hotplug script /etc/hotplug/firmware.agent to
  52. determine which directory FIRMWARE_DIR is set to when the script
  53. runs.
  54. If you want to compile the driver as a module ( = code which can be
  55. inserted in and removed from the running kernel whenever you want),
  56. say M here and read <file:Documentation/kbuild/modules.txt>. The
  57. module will be called iwlagn.ko.
  58. config IWLAGN_SPECTRUM_MEASUREMENT
  59. bool "Enable Spectrum Measurement in iwlagn driver"
  60. depends on IWLAGN
  61. ---help---
  62. This option will enable spectrum measurement for the iwlagn driver.
  63. config IWLAGN_LEDS
  64. bool "Enable LEDS features in iwlagn driver"
  65. depends on IWLAGN
  66. select IWLWIFI_LEDS
  67. ---help---
  68. This option enables LEDS for the iwlagn drivers
  69. config IWL4965
  70. bool "Intel Wireless WiFi 4965AGN"
  71. depends on IWLAGN
  72. ---help---
  73. This option enables support for Intel Wireless WiFi Link 4965AGN
  74. config IWL5000
  75. bool "Intel Wireless WiFi 5000AGN"
  76. depends on IWLAGN
  77. ---help---
  78. This option enables support for Intel Wireless WiFi Link 5000AGN Family
  79. config IWL3945
  80. tristate "Intel PRO/Wireless 3945ABG/BG Network Connection"
  81. depends on PCI && MAC80211 && WLAN_80211 && EXPERIMENTAL
  82. select FW_LOADER
  83. select IWLWIFI
  84. select MAC80211_LEDS if IWL3945_LEDS
  85. select LEDS_CLASS if IWL3945_LEDS
  86. select RFKILL if IWL3945_RFKILL
  87. ---help---
  88. Select to build the driver supporting the:
  89. Intel PRO/Wireless 3945ABG/BG Network Connection
  90. This driver uses the kernel's mac80211 subsystem.
  91. In order to use this driver, you will need a microcode (uCode)
  92. image for it. You can obtain the microcode from:
  93. <http://intellinuxwireless.org/>.
  94. The microcode is typically installed in /lib/firmware. You can
  95. look in the hotplug script /etc/hotplug/firmware.agent to
  96. determine which directory FIRMWARE_DIR is set to when the script
  97. runs.
  98. If you want to compile the driver as a module ( = code which can be
  99. inserted in and removed from the running kernel whenever you want),
  100. say M here and read <file:Documentation/kbuild/modules.txt>. The
  101. module will be called iwl3945.ko.
  102. config IWL3945_RFKILL
  103. bool "Enable RF kill support in iwl3945 drivers"
  104. depends on IWL3945
  105. config IWL3945_SPECTRUM_MEASUREMENT
  106. bool "Enable Spectrum Measurement in iwl3945 drivers"
  107. depends on IWL3945
  108. ---help---
  109. This option will enable spectrum measurement for the iwl3945 driver.
  110. config IWL3945_LEDS
  111. bool "Enable LEDS features in iwl3945 driver"
  112. depends on IWL3945
  113. ---help---
  114. This option enables LEDS for the iwl3945 driver.
  115. config IWL3945_DEBUG
  116. bool "Enable full debugging output in iwl3945 driver"
  117. depends on IWL3945
  118. ---help---
  119. This option will enable debug tracing output for the iwl3945
  120. driver.
  121. This will result in the kernel module being ~100k larger. You can
  122. control which debug output is sent to the kernel log by setting the
  123. value in
  124. /sys/bus/pci/drivers/${DRIVER}/debug_level
  125. This entry will only exist if this option is enabled.
  126. To set a value, simply echo an 8-byte hex value to the same file:
  127. % echo 0x43fff > /sys/bus/pci/drivers/${DRIVER}/debug_level
  128. You can find the list of debug mask values in:
  129. drivers/net/wireless/iwlwifi/iwl-3945-debug.h
  130. If this is your first time using this driver, you should say Y here
  131. as the debug information can assist others in helping you resolve
  132. any problems you may encounter.