Kconfig 4.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123
  1. config IWLWIFI
  2. tristate "Intel Wireless Wifi"
  3. depends on PCI && MAC80211
  4. select FW_LOADER
  5. config IWLWIFI_DEBUG
  6. bool "Enable full debugging output in iwlagn and iwl3945 drivers"
  7. depends on IWLWIFI
  8. ---help---
  9. This option will enable debug tracing output for the iwlwifi drivers
  10. This will result in the kernel module being ~100k larger. You can
  11. control which debug output is sent to the kernel log by setting the
  12. value in
  13. /sys/class/net/wlan0/device/debug_level
  14. This entry will only exist if this option is enabled.
  15. To set a value, simply echo an 8-byte hex value to the same file:
  16. % echo 0x43fff > /sys/class/net/wlan0/device/debug_level
  17. You can find the list of debug mask values in:
  18. drivers/net/wireless/iwlwifi/iwl-debug.h
  19. If this is your first time using this driver, you should say Y here
  20. as the debug information can assist others in helping you resolve
  21. any problems you may encounter.
  22. config IWLWIFI_DEBUGFS
  23. bool "iwlagn debugfs support"
  24. depends on IWLWIFI && MAC80211_DEBUGFS
  25. ---help---
  26. Enable creation of debugfs files for the iwlwifi drivers. This
  27. is a low-impact option that allows getting insight into the
  28. driver's state at runtime.
  29. config IWLWIFI_DEVICE_TRACING
  30. bool "iwlwifi device access tracing"
  31. depends on IWLWIFI
  32. depends on EVENT_TRACING
  33. help
  34. Say Y here to trace all commands, including TX frames and IO
  35. accesses, sent to the device. If you say yes, iwlwifi will
  36. register with the ftrace framework for event tracing and dump
  37. all this information to the ringbuffer, you may need to
  38. increase the ringbuffer size. See the ftrace documentation
  39. for more information.
  40. When tracing is not enabled, this option still has some
  41. (though rather small) overhead.
  42. If unsure, say Y so we can help you better when problems
  43. occur.
  44. config IWLAGN
  45. tristate "Intel Wireless WiFi Next Gen AGN (iwlagn)"
  46. depends on IWLWIFI
  47. ---help---
  48. Select to build the driver supporting the:
  49. Intel Wireless WiFi Link Next-Gen AGN
  50. This driver uses the kernel's mac80211 subsystem.
  51. In order to use this driver, you will need a microcode (uCode)
  52. image for it. You can obtain the microcode from:
  53. <http://intellinuxwireless.org/>.
  54. The microcode is typically installed in /lib/firmware. You can
  55. look in the hotplug script /etc/hotplug/firmware.agent to
  56. determine which directory FIRMWARE_DIR is set to when the script
  57. runs.
  58. If you want to compile the driver as a module ( = code which can be
  59. inserted in and removed from the running kernel whenever you want),
  60. say M here and read <file:Documentation/kbuild/modules.txt>. The
  61. module will be called iwlagn.
  62. config IWL4965
  63. bool "Intel Wireless WiFi 4965AGN"
  64. depends on IWLAGN
  65. ---help---
  66. This option enables support for Intel Wireless WiFi Link 4965AGN
  67. config IWL5000
  68. bool "Intel Wireless-N/Advanced-N/Ultimate-N WiFi Link"
  69. depends on IWLAGN
  70. ---help---
  71. This option enables support for use with the following hardware:
  72. Intel Wireless WiFi Link 6250AGN Adapter
  73. Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN)
  74. Intel WiFi Link 1000BGN
  75. Intel Wireless WiFi 5150AGN
  76. Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN
  77. config IWL3945
  78. tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)"
  79. depends on IWLWIFI
  80. ---help---
  81. Select to build the driver supporting the:
  82. Intel PRO/Wireless 3945ABG/BG Network Connection
  83. This driver uses the kernel's mac80211 subsystem.
  84. In order to use this driver, you will need a microcode (uCode)
  85. image for it. You can obtain the microcode from:
  86. <http://intellinuxwireless.org/>.
  87. The microcode is typically installed in /lib/firmware. You can
  88. look in the hotplug script /etc/hotplug/firmware.agent to
  89. determine which directory FIRMWARE_DIR is set to when the script
  90. runs.
  91. If you want to compile the driver as a module ( = code which can be
  92. inserted in and removed from the running kernel whenever you want),
  93. say M here and read <file:Documentation/kbuild/modules.txt>. The
  94. module will be called iwl3945.