1*4882a593Smuzhiyun# SPDX-License-Identifier: GPL-2.0-only 2*4882a593Smuzhiyun# 3*4882a593Smuzhiyun# Arcnet configuration 4*4882a593Smuzhiyun# 5*4882a593Smuzhiyun 6*4882a593Smuzhiyunmenuconfig ARCNET 7*4882a593Smuzhiyun depends on NETDEVICES && (ISA || PCI || PCMCIA) 8*4882a593Smuzhiyun tristate "ARCnet support" 9*4882a593Smuzhiyun help 10*4882a593Smuzhiyun If you have a network card of this type, say Y and check out the 11*4882a593Smuzhiyun (arguably) beautiful poetry in 12*4882a593Smuzhiyun <file:Documentation/networking/arcnet.rst>. 13*4882a593Smuzhiyun 14*4882a593Smuzhiyun You need both this driver, and the driver for the particular ARCnet 15*4882a593Smuzhiyun chipset of your card. If you don't know, then it's probably a 16*4882a593Smuzhiyun COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset 17*4882a593Smuzhiyun support" below. 18*4882a593Smuzhiyun 19*4882a593Smuzhiyun To compile this driver as a module, choose M here. The module will 20*4882a593Smuzhiyun be called arcnet. 21*4882a593Smuzhiyun 22*4882a593Smuzhiyunif ARCNET 23*4882a593Smuzhiyun 24*4882a593Smuzhiyunconfig ARCNET_1201 25*4882a593Smuzhiyun tristate "Enable standard ARCNet packet format (RFC 1201)" 26*4882a593Smuzhiyun help 27*4882a593Smuzhiyun This allows you to use RFC1201 with your ARCnet card via the virtual 28*4882a593Smuzhiyun arc0 device. You need to say Y here to communicate with 29*4882a593Smuzhiyun industry-standard RFC1201 implementations, like the arcether.com 30*4882a593Smuzhiyun packet driver or most DOS/Windows ODI drivers. Please read the 31*4882a593Smuzhiyun ARCnet documentation in <file:Documentation/networking/arcnet.rst> 32*4882a593Smuzhiyun for more information about using arc0. 33*4882a593Smuzhiyun 34*4882a593Smuzhiyunconfig ARCNET_1051 35*4882a593Smuzhiyun tristate "Enable old ARCNet packet format (RFC 1051)" 36*4882a593Smuzhiyun help 37*4882a593Smuzhiyun This allows you to use RFC1051 with your ARCnet card via the virtual 38*4882a593Smuzhiyun arc0s device. You only need arc0s if you want to talk to ARCnet 39*4882a593Smuzhiyun software complying with the "old" standard, specifically, the DOS 40*4882a593Smuzhiyun arcnet.com packet driver, Amigas running AmiTCP, and some variants 41*4882a593Smuzhiyun of NetBSD. You do not need to say Y here to communicate with 42*4882a593Smuzhiyun industry-standard RFC1201 implementations, like the arcether.com 43*4882a593Smuzhiyun packet driver or most DOS/Windows ODI drivers. RFC1201 is included 44*4882a593Smuzhiyun automatically as the arc0 device. Please read the ARCnet 45*4882a593Smuzhiyun documentation in <file:Documentation/networking/arcnet.rst> for more 46*4882a593Smuzhiyun information about using arc0e and arc0s. 47*4882a593Smuzhiyun 48*4882a593Smuzhiyunconfig ARCNET_RAW 49*4882a593Smuzhiyun tristate "Enable raw mode packet interface" 50*4882a593Smuzhiyun help 51*4882a593Smuzhiyun ARCnet "raw mode" packet encapsulation, no soft headers. Unlikely 52*4882a593Smuzhiyun to work unless talking to a copy of the same Linux arcnet driver, 53*4882a593Smuzhiyun but perhaps marginally faster in that case. 54*4882a593Smuzhiyun 55*4882a593Smuzhiyunconfig ARCNET_CAP 56*4882a593Smuzhiyun tristate "Enable CAP mode packet interface" 57*4882a593Smuzhiyun help 58*4882a593Smuzhiyun ARCnet "cap mode" packet encapsulation. Used to get the hardware 59*4882a593Smuzhiyun acknowledge back to userspace. After the initial protocol byte every 60*4882a593Smuzhiyun packet is stuffed with an extra 4 byte "cookie" which doesn't 61*4882a593Smuzhiyun actually appear on the network. After transmit the driver will send 62*4882a593Smuzhiyun back a packet with protocol byte 0 containing the status of the 63*4882a593Smuzhiyun transmission: 64*4882a593Smuzhiyun 0=no hardware acknowledge 65*4882a593Smuzhiyun 1=excessive nak 66*4882a593Smuzhiyun 2=transmission accepted by the receiver hardware 67*4882a593Smuzhiyun 68*4882a593Smuzhiyun Received packets are also stuffed with the extra 4 bytes but it will 69*4882a593Smuzhiyun be random data. 70*4882a593Smuzhiyun 71*4882a593Smuzhiyun Cap only listens to protocol 1-8. 72*4882a593Smuzhiyun 73*4882a593Smuzhiyunconfig ARCNET_COM90xx 74*4882a593Smuzhiyun tristate "ARCnet COM90xx (normal) chipset driver" 75*4882a593Smuzhiyun help 76*4882a593Smuzhiyun This is the chipset driver for the standard COM90xx cards. If you 77*4882a593Smuzhiyun have always used the old ARCnet driver without knowing what type of 78*4882a593Smuzhiyun card you had, this is probably the one for you. 79*4882a593Smuzhiyun 80*4882a593Smuzhiyun To compile this driver as a module, choose M here. The module will 81*4882a593Smuzhiyun be called com90xx. 82*4882a593Smuzhiyun 83*4882a593Smuzhiyunconfig ARCNET_COM90xxIO 84*4882a593Smuzhiyun tristate "ARCnet COM90xx (IO mapped) chipset driver" 85*4882a593Smuzhiyun help 86*4882a593Smuzhiyun This is the chipset driver for the COM90xx cards, using them in 87*4882a593Smuzhiyun IO-mapped mode instead of memory-mapped mode. This is slower than 88*4882a593Smuzhiyun the normal driver. Only use it if your card doesn't support shared 89*4882a593Smuzhiyun memory. 90*4882a593Smuzhiyun 91*4882a593Smuzhiyun To compile this driver as a module, choose M here. The module will 92*4882a593Smuzhiyun be called com90io. 93*4882a593Smuzhiyun 94*4882a593Smuzhiyunconfig ARCNET_RIM_I 95*4882a593Smuzhiyun tristate "ARCnet COM90xx (RIM I) chipset driver" 96*4882a593Smuzhiyun help 97*4882a593Smuzhiyun This is yet another chipset driver for the COM90xx cards, but this 98*4882a593Smuzhiyun time only using memory-mapped mode, and no IO ports at all. This 99*4882a593Smuzhiyun driver is completely untested, so if you have one of these cards, 100*4882a593Smuzhiyun please mail <dwmw2@infradead.org>, especially if it works! 101*4882a593Smuzhiyun 102*4882a593Smuzhiyun To compile this driver as a module, choose M here. The module will 103*4882a593Smuzhiyun be called arc-rimi. 104*4882a593Smuzhiyun 105*4882a593Smuzhiyunconfig ARCNET_COM20020 106*4882a593Smuzhiyun tristate "ARCnet COM20020 chipset driver" 107*4882a593Smuzhiyun depends on LEDS_CLASS 108*4882a593Smuzhiyun help 109*4882a593Smuzhiyun This is the driver for the new COM20020 chipset. It supports such 110*4882a593Smuzhiyun things as promiscuous mode, so packet sniffing is possible, and 111*4882a593Smuzhiyun extra diagnostic information. 112*4882a593Smuzhiyun 113*4882a593Smuzhiyun To compile this driver as a module, choose M here. The module will 114*4882a593Smuzhiyun be called com20020. 115*4882a593Smuzhiyun 116*4882a593Smuzhiyunconfig ARCNET_COM20020_ISA 117*4882a593Smuzhiyun tristate "Support for COM20020 on ISA" 118*4882a593Smuzhiyun depends on ARCNET_COM20020 && ISA 119*4882a593Smuzhiyun 120*4882a593Smuzhiyunconfig ARCNET_COM20020_PCI 121*4882a593Smuzhiyun tristate "Support for COM20020 on PCI" 122*4882a593Smuzhiyun depends on ARCNET_COM20020 && PCI 123*4882a593Smuzhiyun 124*4882a593Smuzhiyunconfig ARCNET_COM20020_CS 125*4882a593Smuzhiyun tristate "COM20020 ARCnet PCMCIA support" 126*4882a593Smuzhiyun depends on ARCNET_COM20020 && PCMCIA 127*4882a593Smuzhiyun help 128*4882a593Smuzhiyun Say Y here if you intend to attach this type of ARCnet PCMCIA card 129*4882a593Smuzhiyun to your computer. 130*4882a593Smuzhiyun 131*4882a593Smuzhiyun To compile this driver as a module, choose M here: the module will be 132*4882a593Smuzhiyun called com20020_cs. If unsure, say N. 133*4882a593Smuzhiyun 134*4882a593Smuzhiyunendif # ARCNET 135