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