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