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