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