diff options
Diffstat (limited to 'drivers/net/arcnet/Kconfig')
| -rw-r--r-- | drivers/net/arcnet/Kconfig | 39 |
1 files changed, 20 insertions, 19 deletions
diff --git a/drivers/net/arcnet/Kconfig b/drivers/net/arcnet/Kconfig index 39bd16f3f86d..d1d07a1d4fbc 100644 --- a/drivers/net/arcnet/Kconfig +++ b/drivers/net/arcnet/Kconfig @@ -1,14 +1,15 @@ +# SPDX-License-Identifier: GPL-2.0-only # # Arcnet configuration # menuconfig ARCNET - depends on NETDEVICES && (ISA || PCI || PCMCIA) + depends on NETDEVICES && (ISA || PCI || PCMCIA) && HAS_IOPORT tristate "ARCnet support" - ---help--- + help If you have a network card of this type, say Y and check out the (arguably) beautiful poetry in - <file:Documentation/networking/arcnet.txt>. + <file:Documentation/networking/arcnet.rst>. You need both this driver, and the driver for the particular ARCnet chipset of your card. If you don't know, then it's probably a @@ -27,12 +28,12 @@ config ARCNET_1201 arc0 device. You need to say Y here to communicate with industry-standard RFC1201 implementations, like the arcether.com packet driver or most DOS/Windows ODI drivers. Please read the - ARCnet documentation in <file:Documentation/networking/arcnet.txt> + ARCnet documentation in <file:Documentation/networking/arcnet.rst> for more information about using arc0. config ARCNET_1051 tristate "Enable old ARCNet packet format (RFC 1051)" - ---help--- + help This allows you to use RFC1051 with your ARCnet card via the virtual arc0s device. You only need arc0s if you want to talk to ARCnet software complying with the "old" standard, specifically, the DOS @@ -41,7 +42,7 @@ config ARCNET_1051 industry-standard RFC1201 implementations, like the arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201 is included automatically as the arc0 device. Please read the ARCnet - documentation in <file:Documentation/networking/arcnet.txt> for more + documentation in <file:Documentation/networking/arcnet.rst> for more information about using arc0e and arc0s. config ARCNET_RAW @@ -55,19 +56,19 @@ config ARCNET_CAP tristate "Enable CAP mode packet interface" help ARCnet "cap mode" packet encapsulation. Used to get the hardware - acknowledge back to userspace. After the initial protocol byte every - packet is stuffed with an extra 4 byte "cookie" which doesn't - actually appear on the network. After transmit the driver will send - back a packet with protocol byte 0 containing the status of the - transmission: - 0=no hardware acknowledge - 1=excessive nak - 2=transmission accepted by the receiver hardware + acknowledge back to userspace. After the initial protocol byte every + packet is stuffed with an extra 4 byte "cookie" which doesn't + actually appear on the network. After transmit the driver will send + back a packet with protocol byte 0 containing the status of the + transmission: + 0=no hardware acknowledge + 1=excessive nak + 2=transmission accepted by the receiver hardware - Received packets are also stuffed with the extra 4 bytes but it will - be random data. + Received packets are also stuffed with the extra 4 bytes but it will + be random data. - Cap only listens to protocol 1-8. + Cap only listens to protocol 1-8. config ARCNET_COM90xx tristate "ARCnet COM90xx (normal) chipset driver" @@ -81,7 +82,7 @@ config ARCNET_COM90xx config ARCNET_COM90xxIO tristate "ARCnet COM90xx (IO mapped) chipset driver" - ---help--- + help This is the chipset driver for the COM90xx cards, using them in IO-mapped mode instead of memory-mapped mode. This is slower than the normal driver. Only use it if your card doesn't support shared @@ -92,7 +93,7 @@ config ARCNET_COM90xxIO config ARCNET_RIM_I tristate "ARCnet COM90xx (RIM I) chipset driver" - ---help--- + help This is yet another chipset driver for the COM90xx cards, but this time only using memory-mapped mode, and no IO ports at all. This driver is completely untested, so if you have one of these cards, |