Kconfig 3.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  1. config IWLEGACY
  2. tristate
  3. select FW_LOADER
  4. select NEW_LEDS
  5. select LEDS_CLASS
  6. select LEDS_TRIGGERS
  7. select MAC80211_LEDS
  8. config IWL4965
  9. tristate "Intel Wireless WiFi 4965AGN (iwl4965)"
  10. depends on PCI && 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.txt>. 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. select IWLEGACY
  32. ---help---
  33. Select to build the driver supporting the:
  34. Intel PRO/Wireless 3945ABG/BG Network Connection
  35. This driver uses the kernel's mac80211 subsystem.
  36. In order to use this driver, you will need a microcode (uCode)
  37. image for it. You can obtain the microcode from:
  38. <http://intellinuxwireless.org/>.
  39. The microcode is typically installed in /lib/firmware. You can
  40. look in the hotplug script /etc/hotplug/firmware.agent to
  41. determine which directory FIRMWARE_DIR is set to when the script
  42. runs.
  43. If you want to compile the driver as a module ( = code which can be
  44. inserted in and removed from the running kernel whenever you want),
  45. say M here and read <file:Documentation/kbuild/modules.txt>. The
  46. module will be called iwl3945.
  47. menu "iwl3945 / iwl4965 Debugging Options"
  48. depends on IWLEGACY
  49. config IWLEGACY_DEBUG
  50. bool "Enable full debugging output in iwlegacy (iwl 3945/4965) drivers"
  51. depends on IWLEGACY
  52. ---help---
  53. This option will enable debug tracing output for the iwlegacy
  54. drivers.
  55. This will result in the kernel module being ~100k larger. You can
  56. control which debug output is sent to the kernel log by setting the
  57. value in
  58. /sys/class/net/wlan0/device/debug_level
  59. This entry will only exist if this option is enabled.
  60. To set a value, simply echo an 8-byte hex value to the same file:
  61. % echo 0x43fff > /sys/class/net/wlan0/device/debug_level
  62. You can find the list of debug mask values in:
  63. drivers/net/wireless/iwlegacy/common.h
  64. If this is your first time using this driver, you should say Y here
  65. as the debug information can assist others in helping you resolve
  66. any problems you may encounter.
  67. config IWLEGACY_DEBUGFS
  68. bool "iwlegacy (iwl 3945/4965) debugfs support"
  69. depends on IWLEGACY && MAC80211_DEBUGFS
  70. ---help---
  71. Enable creation of debugfs files for the iwlegacy drivers. This
  72. is a low-impact option that allows getting insight into the
  73. driver's state at runtime.
  74. endmenu