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