Kconfig 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. config IWLEGACY
  3. tristate
  4. select FW_LOADER
  5. select LEDS_TRIGGERS
  6. select MAC80211_LEDS
  7. config IWL4965
  8. tristate "Intel Wireless WiFi 4965AGN (iwl4965)"
  9. depends on PCI && MAC80211
  10. depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211
  11. select IWLEGACY
  12. help
  13. This option enables support for
  14. Select to build the driver supporting the:
  15. Intel Wireless WiFi Link 4965AGN
  16. This driver uses the kernel's mac80211 subsystem.
  17. In order to use this driver, you will need a microcode (uCode)
  18. image for it. You can obtain the microcode from:
  19. <http://intellinuxwireless.org/>.
  20. The microcode is typically installed in /lib/firmware. You can
  21. look in the hotplug script /etc/hotplug/firmware.agent to
  22. determine which directory FIRMWARE_DIR is set to when the script
  23. runs.
  24. If you want to compile the driver as a module ( = code which can be
  25. inserted in and removed from the running kernel whenever you want),
  26. say M here and read <file:Documentation/kbuild/modules.rst>. The
  27. module will be called iwl4965.
  28. config IWL3945
  29. tristate "Intel PRO/Wireless 3945ABG/BG Network Connection (iwl3945)"
  30. depends on PCI && MAC80211
  31. depends on LEDS_CLASS=y || LEDS_CLASS=MAC80211
  32. select IWLEGACY
  33. help
  34. Select to build the driver supporting the:
  35. Intel PRO/Wireless 3945ABG/BG Network Connection
  36. This driver uses the kernel's mac80211 subsystem.
  37. In order to use this driver, you will need a microcode (uCode)
  38. image for it. You can obtain the microcode from:
  39. <http://intellinuxwireless.org/>.
  40. The microcode is typically installed in /lib/firmware. You can
  41. look in the hotplug script /etc/hotplug/firmware.agent to
  42. determine which directory FIRMWARE_DIR is set to when the script
  43. runs.
  44. If you want to compile the driver as a module ( = code which can be
  45. inserted in and removed from the running kernel whenever you want),
  46. say M here and read <file:Documentation/kbuild/modules.rst>. The
  47. module will be called iwl3945.
  48. menu "iwl3945 / iwl4965 Debugging Options"
  49. depends on IWLEGACY
  50. config IWLEGACY_DEBUG
  51. bool "Enable full debugging output in iwlegacy (iwl 3945/4965) drivers"
  52. depends on IWLEGACY
  53. help
  54. This option will enable debug tracing output for the iwlegacy
  55. 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/class/net/wlan0/device/debug_level
  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/class/net/wlan0/device/debug_level
  63. You can find the list of debug mask values in:
  64. drivers/net/wireless/iwlegacy/common.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 IWLEGACY_DEBUGFS
  69. bool "iwlegacy (iwl 3945/4965) debugfs support"
  70. depends on IWLEGACY && MAC80211_DEBUGFS
  71. help
  72. Enable creation of debugfs files for the iwlegacy drivers. This
  73. is a low-impact option that allows getting insight into the
  74. driver's state at runtime.
  75. endmenu