drivers/net/wireless/iwlegacy/Kconfig

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