drivers: net: Fix Kconfig indentation · tjh.dev/kernel@02bc5eb

tjh.dev / kernel

fork atom

Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

kernel os linux

fork atom

drivers: net: Fix Kconfig indentation

Adjust indentation from spaces to tab (+optional two spaces) as in
coding style with command like:
$ sed -e 's/^ /\t/' -i */Kconfig

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Acked-by: Kalle Valo <kvalo@codeaurora.org>
Reviewed-by: Leon Romanovsky <leonro@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

authored by

Krzysztof Kozlowski and committed by

David S. Miller 6 years ago 02bc5eb9 bf69abad

+149 -149

19 changed files

expand all collapse all

drivers

net

Kconfig

arcnet

Kconfig

can

usb

Kconfig

ethernet

allwinner

Kconfig

emulex

benet

Kconfig

mellanox

mlx5

core

Kconfig

nxp

Kconfig

pensando

Kconfig

phy

Kconfig

wireless

ath

Kconfig

ar5523

Kconfig

ath6kl

Kconfig

ath9k

Kconfig

carl9170

Kconfig

atmel

Kconfig

intel

ipw2x00

Kconfig

iwlegacy

Kconfig

iwlwifi

Kconfig

ralink

rt2x00

Kconfig

+1 -1

drivers/net/Kconfig

reviewed

··· 487 487 depends on ACPI 488 488 help 489 489 This driver provides support for Extended Socket network device 490 490 - on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series. 490 490 + on Extended Partitioning of FUJITSU PRIMEQUEST 2000 E2 series. 491 491 492 492 config THUNDERBOLT_NET 493 493 tristate "Networking over Thunderbolt cable"

+11 -11

drivers/net/arcnet/Kconfig

reviewed

··· 56 56 tristate "Enable CAP mode packet interface" 57 57 help 58 58 ARCnet "cap mode" packet encapsulation. Used to get the hardware 59 59 - acknowledge back to userspace. After the initial protocol byte every 60 60 - packet is stuffed with an extra 4 byte "cookie" which doesn't 61 61 - actually appear on the network. After transmit the driver will send 62 62 - back a packet with protocol byte 0 containing the status of the 63 63 - transmission: 64 64 - 0=no hardware acknowledge 65 65 - 1=excessive nak 66 66 - 2=transmission accepted by the receiver hardware 59 59 + acknowledge back to userspace. After the initial protocol byte every 60 60 + packet is stuffed with an extra 4 byte "cookie" which doesn't 61 61 + actually appear on the network. After transmit the driver will send 62 62 + back a packet with protocol byte 0 containing the status of the 63 63 + transmission: 64 64 + 0=no hardware acknowledge 65 65 + 1=excessive nak 66 66 + 2=transmission accepted by the receiver hardware 67 67 68 68 - Received packets are also stuffed with the extra 4 bytes but it will 69 69 - be random data. 68 68 + Received packets are also stuffed with the extra 4 bytes but it will 69 69 + be random data. 70 70 71 71 - Cap only listens to protocol 1-8. 71 71 + Cap only listens to protocol 1-8. 72 72 73 73 config ARCNET_COM90xx 74 74 tristate "ARCnet COM90xx (normal) chipset driver"

+4 -4

drivers/net/can/usb/Kconfig

reviewed

··· 15 15 from EMS Dr. Thomas Wuensche (http://www.ems-wuensche.de). 16 16 17 17 config CAN_ESD_USB2 18 18 - tristate "ESD USB/2 CAN/USB interface" 19 19 - ---help--- 20 20 - This driver supports the CAN-USB/2 interface 21 21 - from esd electronic system design gmbh (http://www.esd.eu). 18 18 + tristate "ESD USB/2 CAN/USB interface" 19 19 + ---help--- 20 20 + This driver supports the CAN-USB/2 interface 21 21 + from esd electronic system design gmbh (http://www.esd.eu). 22 22 23 23 config CAN_GS_USB 24 24 tristate "Geschwister Schneider UG interfaces"

+5 -5

drivers/net/ethernet/allwinner/Kconfig

reviewed

··· 21 21 if NET_VENDOR_ALLWINNER 22 22 23 23 config SUN4I_EMAC 24 24 - tristate "Allwinner A10 EMAC support" 24 24 + tristate "Allwinner A10 EMAC support" 25 25 depends on ARCH_SUNXI 26 26 depends on OF 27 27 select CRC32 28 28 select MII 29 29 select PHYLIB 30 30 select MDIO_SUN4I 31 31 - ---help--- 32 32 - Support for Allwinner A10 EMAC ethernet driver. 31 31 + ---help--- 32 32 + Support for Allwinner A10 EMAC ethernet driver. 33 33 34 34 - To compile this driver as a module, choose M here. The module 35 35 - will be called sun4i-emac. 34 34 + To compile this driver as a module, choose M here. The module 35 35 + will be called sun4i-emac. 36 36 37 37 endif # NET_VENDOR_ALLWINNER

+1 -1

drivers/net/ethernet/emulex/benet/Kconfig

reviewed

··· 48 48 chipsets. (e.g. OneConnect OCe14xxx) 49 49 50 50 comment "WARNING: be2net is useless without any enabled chip" 51 51 - depends on BE2NET_BE2=n && BE2NET_BE3=n && BE2NET_LANCER=n && \ 51 51 + depends on BE2NET_BE2=n && BE2NET_BE3=n && BE2NET_LANCER=n && \ 52 52 BE2NET_SKYHAWK=n && BE2NET

+18 -18

drivers/net/ethernet/mellanox/mlx5/core/Kconfig

reviewed

··· 20 20 bool 21 21 22 22 config MLX5_FPGA 23 23 - bool "Mellanox Technologies Innova support" 24 24 - depends on MLX5_CORE 23 23 + bool "Mellanox Technologies Innova support" 24 24 + depends on MLX5_CORE 25 25 select MLX5_ACCEL 26 26 - ---help--- 27 27 - Build support for the Innova family of network cards by Mellanox 28 28 - Technologies. Innova network cards are comprised of a ConnectX chip 29 29 - and an FPGA chip on one board. If you select this option, the 30 30 - mlx5_core driver will include the Innova FPGA core and allow building 31 31 - sandbox-specific client drivers. 26 26 + ---help--- 27 27 + Build support for the Innova family of network cards by Mellanox 28 28 + Technologies. Innova network cards are comprised of a ConnectX chip 29 29 + and an FPGA chip on one board. If you select this option, the 30 30 + mlx5_core driver will include the Innova FPGA core and allow building 31 31 + sandbox-specific client drivers. 32 32 33 33 config MLX5_CORE_EN 34 34 bool "Mellanox 5th generation network adapters (ConnectX series) Ethernet support" ··· 58 58 API. 59 59 60 60 config MLX5_MPFS 61 61 - bool "Mellanox Technologies MLX5 MPFS support" 62 62 - depends on MLX5_CORE_EN 61 61 + bool "Mellanox Technologies MLX5 MPFS support" 62 62 + depends on MLX5_CORE_EN 63 63 default y 64 64 - ---help--- 64 64 + ---help--- 65 65 Mellanox Technologies Ethernet Multi-Physical Function Switch (MPFS) 66 66 - support in ConnectX NIC. MPFs is required for when multi-PF configuration 67 67 - is enabled to allow passing user configured unicast MAC addresses to the 68 68 - requesting PF. 66 66 + support in ConnectX NIC. MPFs is required for when multi-PF configuration 67 67 + is enabled to allow passing user configured unicast MAC addresses to the 68 68 + requesting PF. 69 69 70 70 config MLX5_ESWITCH 71 71 bool "Mellanox Technologies MLX5 SRIOV E-Switch support" ··· 73 73 default y 74 74 ---help--- 75 75 Mellanox Technologies Ethernet SRIOV E-Switch support in ConnectX NIC. 76 76 - E-Switch provides internal SRIOV packet steering and switching for the 77 77 - enabled VFs and PF in two available modes: 78 78 - Legacy SRIOV mode (L2 mac vlan steering based). 79 79 - Switchdev mode (eswitch offloads). 76 76 + E-Switch provides internal SRIOV packet steering and switching for the 77 77 + enabled VFs and PF in two available modes: 78 78 + Legacy SRIOV mode (L2 mac vlan steering based). 79 79 + Switchdev mode (eswitch offloads). 80 80 81 81 config MLX5_CORE_EN_DCB 82 82 bool "Data Center Bridging (DCB) Support"

+4 -4

drivers/net/ethernet/nxp/Kconfig

reviewed

··· 1 1 # SPDX-License-Identifier: GPL-2.0-only 2 2 config LPC_ENET 3 3 - tristate "NXP ethernet MAC on LPC devices" 4 4 - depends on ARCH_LPC32XX || COMPILE_TEST 5 5 - select PHYLIB 6 6 - help 3 3 + tristate "NXP ethernet MAC on LPC devices" 4 4 + depends on ARCH_LPC32XX || COMPILE_TEST 5 5 + select PHYLIB 6 6 + help 7 7 Say Y or M here if you want to use the NXP ethernet MAC included on 8 8 some NXP LPC devices. You can safely enable this option for LPC32xx 9 9 SoC. Also available as a module.

+2 -2

drivers/net/ethernet/pensando/Kconfig

reviewed

··· 26 26 found in 27 27 <file:Documentation/networking/device_drivers/pensando/ionic.rst>. 28 28 29 29 - To compile this driver as a module, choose M here. The module 30 30 - will be called ionic. 29 29 + To compile this driver as a module, choose M here. The module 30 30 + will be called ionic. 31 31 32 32 endif # NET_VENDOR_PENSANDO

+3 -3

drivers/net/phy/Kconfig

reviewed

··· 460 460 Supports the Renesas PHYs uPD60620 and uPD60620A. 461 461 462 462 config ROCKCHIP_PHY 463 463 - tristate "Driver for Rockchip Ethernet PHYs" 464 464 - ---help--- 465 465 - Currently supports the integrated Ethernet PHY. 463 463 + tristate "Driver for Rockchip Ethernet PHYs" 464 464 + ---help--- 465 465 + Currently supports the integrated Ethernet PHY. 466 466 467 467 config SMSC_PHY 468 468 tristate "SMSC PHYs"

+1 -1

drivers/net/wireless/ath/Kconfig

reviewed

··· 34 34 depends on ATH_DEBUG 35 35 depends on EVENT_TRACING 36 36 ---help--- 37 37 - This option enables tracepoints for atheros wireless drivers. 37 37 + This option enables tracepoints for atheros wireless drivers. 38 38 Currently, ath9k makes use of this facility. 39 39 40 40 config ATH_REG_DYNAMIC_USER_REG_HINTS

+2 -2

drivers/net/wireless/ath/ar5523/Kconfig

reviewed

··· 5 5 select ATH_COMMON 6 6 select FW_LOADER 7 7 ---help--- 8 8 - This module add support for AR5523 based USB dongles such as D-Link 9 9 - DWL-G132, Netgear WPN111 and many more. 8 8 + This module add support for AR5523 based USB dongles such as D-Link 9 9 + DWL-G132, Netgear WPN111 and many more.

+1 -1

drivers/net/wireless/ath/ath6kl/Kconfig

reviewed

··· 2 2 config ATH6KL 3 3 tristate "Atheros mobile chipsets support" 4 4 depends on CFG80211 5 5 - ---help--- 5 5 + ---help--- 6 6 This module adds core support for wireless adapters based on 7 7 Atheros AR6003 and AR6004 chipsets. You still need separate 8 8 bus drivers for USB and SDIO to be able to use real devices.

+1 -1

drivers/net/wireless/ath/ath9k/Kconfig

reviewed

··· 148 148 depends on ATH9K 149 149 default n 150 150 ---help--- 151 151 - This option enables channel context support in ath9k, which is needed 151 151 + This option enables channel context support in ath9k, which is needed 152 152 for multi-channel concurrency. Enable this if P2P PowerSave support 153 153 is required. 154 154

+3 -3

drivers/net/wireless/ath/carl9170/Kconfig

reviewed

··· 41 41 default y 42 42 43 43 config CARL9170_HWRNG 44 44 - bool "Random number generator" 45 45 - depends on CARL9170 && (HW_RANDOM = y || HW_RANDOM = CARL9170) 46 46 - default n 44 44 + bool "Random number generator" 45 45 + depends on CARL9170 && (HW_RANDOM = y || HW_RANDOM = CARL9170) 46 46 + default n 47 47 help 48 48 Provides a hardware random number generator to the kernel. 49 49

+16 -16

drivers/net/wireless/atmel/Kconfig

reviewed

··· 20 20 select FW_LOADER 21 21 select CRC32 22 22 ---help--- 23 23 - A driver 802.11b wireless cards based on the Atmel fast-vnet 24 24 - chips. This driver supports standard Linux wireless extensions. 23 23 + A driver 802.11b wireless cards based on the Atmel fast-vnet 24 24 + chips. This driver supports standard Linux wireless extensions. 25 25 26 26 - Many cards based on this chipset do not have flash memory 27 27 - and need their firmware loaded at start-up. If yours is 28 28 - one of these, you will need to provide a firmware image 29 29 - to be loaded into the card by the driver. The Atmel 30 30 - firmware package can be downloaded from 31 31 - <http://www.thekelleys.org.uk/atmel> 26 26 + Many cards based on this chipset do not have flash memory 27 27 + and need their firmware loaded at start-up. If yours is 28 28 + one of these, you will need to provide a firmware image 29 29 + to be loaded into the card by the driver. The Atmel 30 30 + firmware package can be downloaded from 31 31 + <http://www.thekelleys.org.uk/atmel> 32 32 33 33 config PCI_ATMEL 34 34 tristate "Atmel at76c506 PCI cards" 35 35 depends on ATMEL && PCI 36 36 ---help--- 37 37 - Enable support for PCI and mini-PCI cards containing the 38 38 - Atmel at76c506 chip. 37 37 + Enable support for PCI and mini-PCI cards containing the 38 38 + Atmel at76c506 chip. 39 39 40 40 config PCMCIA_ATMEL 41 41 tristate "Atmel at76c502/at76c504 PCMCIA cards" ··· 48 48 Atmel at76c502 and at76c504 chips. 49 49 50 50 config AT76C50X_USB 51 51 - tristate "Atmel at76c503/at76c505/at76c505a USB cards" 52 52 - depends on MAC80211 && USB 53 53 - select FW_LOADER 54 54 - ---help--- 55 55 - Enable support for USB Wireless devices using Atmel at76c503, 56 56 - at76c505 or at76c505a chips. 51 51 + tristate "Atmel at76c503/at76c505/at76c505a USB cards" 52 52 + depends on MAC80211 && USB 53 53 + select FW_LOADER 54 54 + ---help--- 55 55 + Enable support for USB Wireless devices using Atmel at76c503, 56 56 + at76c505 or at76c505a chips. 57 57 58 58 endif # WLAN_VENDOR_ATMEL

+58 -58

drivers/net/wireless/intel/ipw2x00/Kconfig

reviewed

··· 13 13 select LIB80211 14 14 select LIBIPW 15 15 ---help--- 16 16 - A driver for the Intel PRO/Wireless 2100 Network 16 16 + A driver for the Intel PRO/Wireless 2100 Network 17 17 Connection 802.11b wireless network adapter. 18 18 19 19 - See <file:Documentation/networking/device_drivers/intel/ipw2100.txt> 19 19 + See <file:Documentation/networking/device_drivers/intel/ipw2100.txt> 20 20 for information on the capabilities currently enabled in this driver 21 21 and for tips for debugging issues and problems. 22 22 23 23 In order to use this driver, you will need a firmware image for it. 24 24 - You can obtain the firmware from 25 25 - <http://ipw2100.sf.net/>. Once you have the firmware image, you 24 24 + You can obtain the firmware from 25 25 + <http://ipw2100.sf.net/>. Once you have the firmware image, you 26 26 will need to place it in /lib/firmware. 27 27 28 28 - You will also very likely need the Wireless Tools in order to 29 29 - configure your card: 28 28 + You will also very likely need the Wireless Tools in order to 29 29 + configure your card: 30 30 31 31 - <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>. 31 31 + <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>. 32 32 33 33 - It is recommended that you compile this driver as a module (M) 34 34 - rather than built-in (Y). This driver requires firmware at device 35 35 - initialization time, and when built-in this typically happens 36 36 - before the filesystem is accessible (hence firmware will be 37 37 - unavailable and initialization will fail). If you do choose to build 38 38 - this driver into your kernel image, you can avoid this problem by 39 39 - including the firmware and a firmware loader in an initramfs. 40 40 - 33 33 + It is recommended that you compile this driver as a module (M) 34 34 + rather than built-in (Y). This driver requires firmware at device 35 35 + initialization time, and when built-in this typically happens 36 36 + before the filesystem is accessible (hence firmware will be 37 37 + unavailable and initialization will fail). If you do choose to build 38 38 + this driver into your kernel image, you can avoid this problem by 39 39 + including the firmware and a firmware loader in an initramfs. 40 40 + 41 41 config IPW2100_MONITOR 42 42 - bool "Enable promiscuous mode" 43 43 - depends on IPW2100 44 44 - ---help--- 42 42 + bool "Enable promiscuous mode" 43 43 + depends on IPW2100 44 44 + ---help--- 45 45 Enables promiscuous/monitor mode support for the ipw2100 driver. 46 46 - With this feature compiled into the driver, you can switch to 46 46 + With this feature compiled into the driver, you can switch to 47 47 promiscuous mode via the Wireless Tool's Monitor mode. While in this 48 48 mode, no packets can be sent. 49 49 ··· 51 51 bool "Enable full debugging output in IPW2100 module." 52 52 depends on IPW2100 53 53 ---help--- 54 54 - This option will enable debug tracing output for the IPW2100. 54 54 + This option will enable debug tracing output for the IPW2100. 55 55 56 56 - This will result in the kernel module being ~60k larger. You can 57 57 - control which debug output is sent to the kernel log by setting the 58 58 - value in 56 56 + This will result in the kernel module being ~60k larger. You can 57 57 + control which debug output is sent to the kernel log by setting the 58 58 + value in 59 59 60 60 /sys/bus/pci/drivers/ipw2100/debug_level 61 61 62 62 This entry will only exist if this option is enabled. 63 63 64 64 - If you are not trying to debug or develop the IPW2100 driver, you 64 64 + If you are not trying to debug or develop the IPW2100 driver, you 65 65 most likely want to say N here. 66 66 67 67 config IPW2200 ··· 75 75 select LIB80211 76 76 select LIBIPW 77 77 ---help--- 78 78 - A driver for the Intel PRO/Wireless 2200BG and 2915ABG Network 79 79 - Connection adapters. 78 78 + A driver for the Intel PRO/Wireless 2200BG and 2915ABG Network 79 79 + Connection adapters. 80 80 81 81 - See <file:Documentation/networking/device_drivers/intel/ipw2200.txt> 81 81 + See <file:Documentation/networking/device_drivers/intel/ipw2200.txt> 82 82 for information on the capabilities currently enabled in this 83 83 driver and for tips for debugging issues and problems. 84 84 85 85 In order to use this driver, you will need a firmware image for it. 86 86 - You can obtain the firmware from 87 87 - <http://ipw2200.sf.net/>. See the above referenced README.ipw2200 86 86 + You can obtain the firmware from 87 87 + <http://ipw2200.sf.net/>. See the above referenced README.ipw2200 88 88 for information on where to install the firmware images. 89 89 90 90 - You will also very likely need the Wireless Tools in order to 91 91 - configure your card: 90 90 + You will also very likely need the Wireless Tools in order to 91 91 + configure your card: 92 92 93 93 - <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>. 93 93 + <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>. 94 94 95 95 - It is recommended that you compile this driver as a module (M) 96 96 - rather than built-in (Y). This driver requires firmware at device 97 97 - initialization time, and when built-in this typically happens 98 98 - before the filesystem is accessible (hence firmware will be 99 99 - unavailable and initialization will fail). If you do choose to build 100 100 - this driver into your kernel image, you can avoid this problem by 101 101 - including the firmware and a firmware loader in an initramfs. 95 95 + It is recommended that you compile this driver as a module (M) 96 96 + rather than built-in (Y). This driver requires firmware at device 97 97 + initialization time, and when built-in this typically happens 98 98 + before the filesystem is accessible (hence firmware will be 99 99 + unavailable and initialization will fail). If you do choose to build 100 100 + this driver into your kernel image, you can avoid this problem by 101 101 + including the firmware and a firmware loader in an initramfs. 102 102 103 103 config IPW2200_MONITOR 104 104 - bool "Enable promiscuous mode" 105 105 - depends on IPW2200 106 106 - ---help--- 104 104 + bool "Enable promiscuous mode" 105 105 + depends on IPW2200 106 106 + ---help--- 107 107 Enables promiscuous/monitor mode support for the ipw2200 driver. 108 108 - With this feature compiled into the driver, you can switch to 108 108 + With this feature compiled into the driver, you can switch to 109 109 promiscuous mode via the Wireless Tool's Monitor mode. While in this 110 110 mode, no packets can be sent. 111 111 ··· 118 118 depends on IPW2200_MONITOR 119 119 select IPW2200_RADIOTAP 120 120 ---help--- 121 121 - Enables the creation of a second interface prefixed 'rtap'. 122 122 - This second interface will provide every received in radiotap 121 121 + Enables the creation of a second interface prefixed 'rtap'. 122 122 + This second interface will provide every received in radiotap 123 123 format. 124 124 125 125 - This is useful for performing wireless network analysis while 126 126 - maintaining an active association. 125 125 + This is useful for performing wireless network analysis while 126 126 + maintaining an active association. 127 127 128 128 - Example usage: 128 128 + Example usage: 129 129 130 130 - % modprobe ipw2200 rtap_iface=1 131 131 - % ifconfig rtap0 up 132 132 - % tethereal -i rtap0 130 130 + % modprobe ipw2200 rtap_iface=1 131 131 + % ifconfig rtap0 up 132 132 + % tethereal -i rtap0 133 133 134 134 - If you do not specify 'rtap_iface=1' as a module parameter then 135 135 - the rtap interface will not be created and you will need to turn 136 136 - it on via sysfs: 137 137 - 138 138 - % echo 1 > /sys/bus/pci/drivers/ipw2200/*/rtap_iface 134 134 + If you do not specify 'rtap_iface=1' as a module parameter then 135 135 + the rtap interface will not be created and you will need to turn 136 136 + it on via sysfs: 137 137 + 138 138 + % echo 1 > /sys/bus/pci/drivers/ipw2200/*/rtap_iface 139 139 140 140 config IPW2200_QOS 141 141 - bool "Enable QoS support" 142 142 - depends on IPW2200 141 141 + bool "Enable QoS support" 142 142 + depends on IPW2200 143 143 144 144 config IPW2200_DEBUG 145 145 bool "Enable full debugging output in IPW2200 module."

+3 -3

drivers/net/wireless/intel/iwlegacy/Kconfig

reviewed

··· 91 91 any problems you may encounter. 92 92 93 93 config IWLEGACY_DEBUGFS 94 94 - bool "iwlegacy (iwl 3945/4965) debugfs support" 95 95 - depends on IWLEGACY && MAC80211_DEBUGFS 96 96 - ---help--- 94 94 + bool "iwlegacy (iwl 3945/4965) debugfs support" 95 95 + depends on IWLEGACY && MAC80211_DEBUGFS 96 96 + ---help--- 97 97 Enable creation of debugfs files for the iwlegacy drivers. This 98 98 is a low-impact option that allows getting insight into the 99 99 driver's state at runtime.

+3 -3

drivers/net/wireless/intel/iwlwifi/Kconfig

reviewed

··· 119 119 any problems you may encounter. 120 120 121 121 config IWLWIFI_DEBUGFS 122 122 - bool "iwlwifi debugfs support" 123 123 - depends on MAC80211_DEBUGFS 124 124 - ---help--- 122 122 + bool "iwlwifi debugfs support" 123 123 + depends on MAC80211_DEBUGFS 124 124 + ---help--- 125 125 Enable creation of debugfs files for the iwlwifi drivers. This 126 126 is a low-impact option that allows getting insight into the 127 127 driver's state at runtime.

+12 -12

drivers/net/wireless/ralink/rt2x00/Kconfig

reviewed

··· 98 98 bool "rt2800pci - Include support for rt53xx devices (EXPERIMENTAL)" 99 99 default y 100 100 ---help--- 101 101 - This adds support for rt53xx wireless chipset family to the 102 102 - rt2800pci driver. 103 103 - Supported chips: RT5390 101 101 + This adds support for rt53xx wireless chipset family to the 102 102 + rt2800pci driver. 103 103 + Supported chips: RT5390 104 104 105 105 config RT2800PCI_RT3290 106 106 bool "rt2800pci - Include support for rt3290 devices (EXPERIMENTAL)" 107 107 default y 108 108 ---help--- 109 109 - This adds support for rt3290 wireless chipset family to the 110 110 - rt2800pci driver. 111 111 - Supported chips: RT3290 109 109 + This adds support for rt3290 wireless chipset family to the 110 110 + rt2800pci driver. 111 111 + Supported chips: RT3290 112 112 endif 113 113 114 114 config RT2500USB ··· 176 176 config RT2800USB_RT53XX 177 177 bool "rt2800usb - Include support for rt53xx devices (EXPERIMENTAL)" 178 178 ---help--- 179 179 - This adds support for rt53xx wireless chipset family to the 180 180 - rt2800usb driver. 181 181 - Supported chips: RT5370 179 179 + This adds support for rt53xx wireless chipset family to the 180 180 + rt2800usb driver. 181 181 + Supported chips: RT5370 182 182 183 183 config RT2800USB_RT55XX 184 184 bool "rt2800usb - Include support for rt55xx devices (EXPERIMENTAL)" 185 185 ---help--- 186 186 - This adds support for rt55xx wireless chipset family to the 187 187 - rt2800usb driver. 188 188 - Supported chips: RT5572 186 186 + This adds support for rt55xx wireless chipset family to the 187 187 + rt2800usb driver. 188 188 + Supported chips: RT5572 189 189 190 190 config RT2800USB_UNKNOWN 191 191 bool "rt2800usb - Include support for unknown (USB) devices"