Wey-Yi Guy | be663ab | 2011-02-21 11:27:26 -0800 | [diff] [blame^] | 1 | config IWLAGN |
| 2 | tristate "Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlagn) " |
Johannes Berg | 1d8c4ae9 | 2010-01-22 14:22:52 -0800 | [diff] [blame] | 3 | depends on PCI && MAC80211 |
Reinette Chatre | 80bc539 | 2009-02-13 11:51:19 -0800 | [diff] [blame] | 4 | select FW_LOADER |
Wey-Yi Guy | 5ed540a | 2011-01-21 15:26:39 -0800 | [diff] [blame] | 5 | select NEW_LEDS |
| 6 | select LEDS_CLASS |
| 7 | select LEDS_TRIGGERS |
| 8 | select MAC80211_LEDS |
Wey-Yi Guy | be663ab | 2011-02-21 11:27:26 -0800 | [diff] [blame^] | 9 | ---help--- |
| 10 | Select to build the driver supporting the: |
| 11 | |
| 12 | Intel Wireless WiFi Link Next-Gen AGN |
| 13 | |
| 14 | This option enables support for use with the following hardware: |
| 15 | Intel Wireless WiFi Link 6250AGN Adapter |
| 16 | Intel 6000 Series Wi-Fi Adapters (6200AGN and 6300AGN) |
| 17 | Intel WiFi Link 1000BGN |
| 18 | Intel Wireless WiFi 5150AGN |
| 19 | Intel Wireless WiFi 5100AGN, 5300AGN, and 5350AGN |
| 20 | Intel 6005 Series Wi-Fi Adapters |
| 21 | Intel 6030 Series Wi-Fi Adapters |
| 22 | Intel Wireless WiFi Link 6150BGN 2 Adapter |
| 23 | Intel 100 Series Wi-Fi Adapters (100BGN and 130BGN) |
| 24 | Intel 2000 Series Wi-Fi Adapters |
| 25 | |
| 26 | |
| 27 | This driver uses the kernel's mac80211 subsystem. |
| 28 | |
| 29 | In order to use this driver, you will need a microcode (uCode) |
| 30 | image for it. You can obtain the microcode from: |
| 31 | |
| 32 | <http://intellinuxwireless.org/>. |
| 33 | |
| 34 | The microcode is typically installed in /lib/firmware. You can |
| 35 | look in the hotplug script /etc/hotplug/firmware.agent to |
| 36 | determine which directory FIRMWARE_DIR is set to when the script |
| 37 | runs. |
| 38 | |
| 39 | If you want to compile the driver as a module ( = code which can be |
| 40 | inserted in and removed from the running kernel whenever you want), |
| 41 | say M here and read <file:Documentation/kbuild/modules.txt>. The |
| 42 | module will be called iwlagn. |
Mohamed Abbas | ab53d8a | 2008-03-25 16:33:36 -0700 | [diff] [blame] | 43 | |
Jay Sternberg | 110ff6db | 2010-08-12 12:15:55 -0700 | [diff] [blame] | 44 | menu "Debugging Options" |
Wey-Yi Guy | be663ab | 2011-02-21 11:27:26 -0800 | [diff] [blame^] | 45 | depends on IWLAGN |
Jay Sternberg | 110ff6db | 2010-08-12 12:15:55 -0700 | [diff] [blame] | 46 | |
Tomas Winkler | 4fc22b2 | 2008-07-21 18:54:42 +0300 | [diff] [blame] | 47 | config IWLWIFI_DEBUG |
Wey-Yi Guy | be663ab | 2011-02-21 11:27:26 -0800 | [diff] [blame^] | 48 | bool "Enable full debugging output in the iwlagn driver" |
| 49 | depends on IWLAGN |
Tomas Winkler | 4fc22b2 | 2008-07-21 18:54:42 +0300 | [diff] [blame] | 50 | ---help--- |
| 51 | This option will enable debug tracing output for the iwlwifi drivers |
| 52 | |
| 53 | This will result in the kernel module being ~100k larger. You can |
| 54 | control which debug output is sent to the kernel log by setting the |
| 55 | value in |
| 56 | |
| 57 | /sys/class/net/wlan0/device/debug_level |
| 58 | |
| 59 | This entry will only exist if this option is enabled. |
| 60 | |
| 61 | To set a value, simply echo an 8-byte hex value to the same file: |
| 62 | |
| 63 | % echo 0x43fff > /sys/class/net/wlan0/device/debug_level |
| 64 | |
| 65 | You can find the list of debug mask values in: |
| 66 | drivers/net/wireless/iwlwifi/iwl-debug.h |
| 67 | |
| 68 | If this is your first time using this driver, you should say Y here |
| 69 | as the debug information can assist others in helping you resolve |
| 70 | any problems you may encounter. |
| 71 | |
| 72 | config IWLWIFI_DEBUGFS |
Reinette Chatre | 80bc539 | 2009-02-13 11:51:19 -0800 | [diff] [blame] | 73 | bool "iwlagn debugfs support" |
Wey-Yi Guy | be663ab | 2011-02-21 11:27:26 -0800 | [diff] [blame^] | 74 | depends on IWLAGN && MAC80211_DEBUGFS |
Tomas Winkler | 4fc22b2 | 2008-07-21 18:54:42 +0300 | [diff] [blame] | 75 | ---help--- |
Johannes Berg | d73e492 | 2010-05-06 12:18:41 -0700 | [diff] [blame] | 76 | Enable creation of debugfs files for the iwlwifi drivers. This |
| 77 | is a low-impact option that allows getting insight into the |
| 78 | driver's state at runtime. |
Tomas Winkler | 4fc22b2 | 2008-07-21 18:54:42 +0300 | [diff] [blame] | 79 | |
Jay Sternberg | 3939608 | 2010-08-12 10:24:07 -0700 | [diff] [blame] | 80 | config IWLWIFI_DEBUG_EXPERIMENTAL_UCODE |
| 81 | bool "Experimental uCode support" |
Wey-Yi Guy | be663ab | 2011-02-21 11:27:26 -0800 | [diff] [blame^] | 82 | depends on IWLAGN && IWLWIFI_DEBUG |
Jay Sternberg | 3939608 | 2010-08-12 10:24:07 -0700 | [diff] [blame] | 83 | ---help--- |
| 84 | Enable use of experimental ucode for testing and debugging. |
| 85 | |
Johannes Berg | be1a71a | 2009-10-02 13:44:02 -0700 | [diff] [blame] | 86 | config IWLWIFI_DEVICE_TRACING |
| 87 | bool "iwlwifi device access tracing" |
Wey-Yi Guy | be663ab | 2011-02-21 11:27:26 -0800 | [diff] [blame^] | 88 | depends on IWLAGN |
Johannes Berg | be1a71a | 2009-10-02 13:44:02 -0700 | [diff] [blame] | 89 | depends on EVENT_TRACING |
| 90 | help |
| 91 | Say Y here to trace all commands, including TX frames and IO |
| 92 | accesses, sent to the device. If you say yes, iwlwifi will |
| 93 | register with the ftrace framework for event tracing and dump |
| 94 | all this information to the ringbuffer, you may need to |
| 95 | increase the ringbuffer size. See the ftrace documentation |
| 96 | for more information. |
| 97 | |
| 98 | When tracing is not enabled, this option still has some |
| 99 | (though rather small) overhead. |
| 100 | |
| 101 | If unsure, say Y so we can help you better when problems |
| 102 | occur. |
Jay Sternberg | 110ff6db | 2010-08-12 12:15:55 -0700 | [diff] [blame] | 103 | endmenu |
Johannes Berg | be1a71a | 2009-10-02 13:44:02 -0700 | [diff] [blame] | 104 | |
Wey-Yi Guy | f35c0c5 | 2011-01-13 17:09:29 -0800 | [diff] [blame] | 105 | config IWL_P2P |
| 106 | bool "iwlwifi experimental P2P support" |
Wey-Yi Guy | be663ab | 2011-02-21 11:27:26 -0800 | [diff] [blame^] | 107 | depends on IWLAGN |
Wey-Yi Guy | f35c0c5 | 2011-01-13 17:09:29 -0800 | [diff] [blame] | 108 | help |
| 109 | This option enables experimental P2P support for some devices |
| 110 | based on microcode support. Since P2P support is still under |
| 111 | development, this option may even enable it for some devices |
| 112 | now that turn out to not support it in the future due to |
| 113 | microcode restrictions. |
| 114 | |
| 115 | To determine if your microcode supports the experimental P2P |
| 116 | offered by this option, check if the driver advertises AP |
| 117 | support when it is loaded. |
| 118 | |
| 119 | Say Y only if you want to experiment with P2P. |
| 120 | |