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