| 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | # |
| 3 | # Arcnet configuration |
| 4 | # |
| 5 | |
| 6 | menuconfig ARCNET |
| 7 | depends on NETDEVICES && PCI && HAS_IOPORT |
| 8 | tristate "ARCnet support" |
| 9 | help |
| 10 | If you have a network card of this type, say Y and check out the |
| 11 | (arguably) beautiful poetry in |
| 12 | <file:Documentation/networking/arcnet.rst>. |
| 13 | |
| 14 | You need both this driver, and the driver for the particular ARCnet |
| 15 | chipset of your card. |
| 16 | |
| 17 | To compile this driver as a module, choose M here. The module will |
| 18 | be called arcnet. |
| 19 | |
| 20 | if ARCNET |
| 21 | |
| 22 | config ARCNET_1201 |
| 23 | tristate "Enable standard ARCNet packet format (RFC 1201)" |
| 24 | help |
| 25 | This allows you to use RFC1201 with your ARCnet card via the virtual |
| 26 | arc0 device. You need to say Y here to communicate with |
| 27 | industry-standard RFC1201 implementations, like the arcether.com |
| 28 | packet driver or most DOS/Windows ODI drivers. Please read the |
| 29 | ARCnet documentation in <file:Documentation/networking/arcnet.rst> |
| 30 | for more information about using arc0. |
| 31 | |
| 32 | config ARCNET_1051 |
| 33 | tristate "Enable old ARCNet packet format (RFC 1051)" |
| 34 | help |
| 35 | This allows you to use RFC1051 with your ARCnet card via the virtual |
| 36 | arc0s device. You only need arc0s if you want to talk to ARCnet |
| 37 | software complying with the "old" standard, specifically, the DOS |
| 38 | arcnet.com packet driver, Amigas running AmiTCP, and some variants |
| 39 | of NetBSD. You do not need to say Y here to communicate with |
| 40 | industry-standard RFC1201 implementations, like the arcether.com |
| 41 | packet driver or most DOS/Windows ODI drivers. RFC1201 is included |
| 42 | automatically as the arc0 device. Please read the ARCnet |
| 43 | documentation in <file:Documentation/networking/arcnet.rst> for more |
| 44 | information about using arc0e and arc0s. |
| 45 | |
| 46 | config ARCNET_RAW |
| 47 | tristate "Enable raw mode packet interface" |
| 48 | help |
| 49 | ARCnet "raw mode" packet encapsulation, no soft headers. Unlikely |
| 50 | to work unless talking to a copy of the same Linux arcnet driver, |
| 51 | but perhaps marginally faster in that case. |
| 52 | |
| 53 | config ARCNET_CAP |
| 54 | tristate "Enable CAP mode packet interface" |
| 55 | help |
| 56 | ARCnet "cap mode" packet encapsulation. Used to get the hardware |
| 57 | acknowledge back to userspace. After the initial protocol byte every |
| 58 | packet is stuffed with an extra 4 byte "cookie" which doesn't |
| 59 | actually appear on the network. After transmit the driver will send |
| 60 | back a packet with protocol byte 0 containing the status of the |
| 61 | transmission: |
| 62 | 0=no hardware acknowledge |
| 63 | 1=excessive nak |
| 64 | 2=transmission accepted by the receiver hardware |
| 65 | |
| 66 | Received packets are also stuffed with the extra 4 bytes but it will |
| 67 | be random data. |
| 68 | |
| 69 | Cap only listens to protocol 1-8. |
| 70 | |
| 71 | config ARCNET_COM20020 |
| 72 | tristate "ARCnet COM20020 chipset driver" |
| 73 | depends on LEDS_CLASS |
| 74 | help |
| 75 | This is the driver for the new COM20020 chipset. It supports such |
| 76 | things as promiscuous mode, so packet sniffing is possible, and |
| 77 | extra diagnostic information. |
| 78 | |
| 79 | To compile this driver as a module, choose M here. The module will |
| 80 | be called com20020. |
| 81 | |
| 82 | config ARCNET_COM20020_PCI |
| 83 | tristate "Support for COM20020 on PCI" |
| 84 | depends on ARCNET_COM20020 && PCI |
| 85 | |
| 86 | endif # ARCNET |