Kconfig 5.3 KB

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