1ec8f24b7SThomas Gleixner# SPDX-License-Identifier: GPL-2.0-only 21da177e4SLinus Torvalds# 31da177e4SLinus Torvalds# Arcnet configuration 41da177e4SLinus Torvalds# 51da177e4SLinus Torvalds 642859007SJan Engelhardtmenuconfig ARCNET 7330278cdSJeff Kirsher depends on NETDEVICES && (ISA || PCI || PCMCIA) 8fc0b927dSBen Hutchings tristate "ARCnet support" 9*a7f7f624SMasahiro Yamada help 101da177e4SLinus Torvalds If you have a network card of this type, say Y and check out the 111da177e4SLinus Torvalds (arguably) beautiful poetry in 1208bab46fSMauro Carvalho Chehab <file:Documentation/networking/arcnet.rst>. 131da177e4SLinus Torvalds 141da177e4SLinus Torvalds You need both this driver, and the driver for the particular ARCnet 151da177e4SLinus Torvalds chipset of your card. If you don't know, then it's probably a 161da177e4SLinus Torvalds COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset 171da177e4SLinus Torvalds support" below. 181da177e4SLinus Torvalds 1957ce45ddSAdrian Bunk To compile this driver as a module, choose M here. The module will 201da177e4SLinus Torvalds be called arcnet. 211da177e4SLinus Torvalds 2242859007SJan Engelhardtif ARCNET 2342859007SJan Engelhardt 241da177e4SLinus Torvaldsconfig ARCNET_1201 251da177e4SLinus Torvalds tristate "Enable standard ARCNet packet format (RFC 1201)" 261da177e4SLinus Torvalds help 271da177e4SLinus Torvalds This allows you to use RFC1201 with your ARCnet card via the virtual 281da177e4SLinus Torvalds arc0 device. You need to say Y here to communicate with 291da177e4SLinus Torvalds industry-standard RFC1201 implementations, like the arcether.com 301da177e4SLinus Torvalds packet driver or most DOS/Windows ODI drivers. Please read the 3108bab46fSMauro Carvalho Chehab ARCnet documentation in <file:Documentation/networking/arcnet.rst> 321da177e4SLinus Torvalds for more information about using arc0. 331da177e4SLinus Torvalds 341da177e4SLinus Torvaldsconfig ARCNET_1051 351da177e4SLinus Torvalds tristate "Enable old ARCNet packet format (RFC 1051)" 36*a7f7f624SMasahiro Yamada help 371da177e4SLinus Torvalds This allows you to use RFC1051 with your ARCnet card via the virtual 381da177e4SLinus Torvalds arc0s device. You only need arc0s if you want to talk to ARCnet 391da177e4SLinus Torvalds software complying with the "old" standard, specifically, the DOS 401da177e4SLinus Torvalds arcnet.com packet driver, Amigas running AmiTCP, and some variants 411da177e4SLinus Torvalds of NetBSD. You do not need to say Y here to communicate with 421da177e4SLinus Torvalds industry-standard RFC1201 implementations, like the arcether.com 431da177e4SLinus Torvalds packet driver or most DOS/Windows ODI drivers. RFC1201 is included 441da177e4SLinus Torvalds automatically as the arc0 device. Please read the ARCnet 4508bab46fSMauro Carvalho Chehab documentation in <file:Documentation/networking/arcnet.rst> for more 461da177e4SLinus Torvalds information about using arc0e and arc0s. 471da177e4SLinus Torvalds 481da177e4SLinus Torvaldsconfig ARCNET_RAW 491da177e4SLinus Torvalds tristate "Enable raw mode packet interface" 501da177e4SLinus Torvalds help 511da177e4SLinus Torvalds ARCnet "raw mode" packet encapsulation, no soft headers. Unlikely 521da177e4SLinus Torvalds to work unless talking to a copy of the same Linux arcnet driver, 531da177e4SLinus Torvalds but perhaps marginally faster in that case. 541da177e4SLinus Torvalds 551da177e4SLinus Torvaldsconfig ARCNET_CAP 561da177e4SLinus Torvalds tristate "Enable CAP mode packet interface" 571da177e4SLinus Torvalds help 581da177e4SLinus Torvalds ARCnet "cap mode" packet encapsulation. Used to get the hardware 591da177e4SLinus Torvalds acknowledge back to userspace. After the initial protocol byte every 601da177e4SLinus Torvalds packet is stuffed with an extra 4 byte "cookie" which doesn't 611da177e4SLinus Torvalds actually appear on the network. After transmit the driver will send 621da177e4SLinus Torvalds back a packet with protocol byte 0 containing the status of the 6347c51431SJon Mason transmission: 641da177e4SLinus Torvalds 0=no hardware acknowledge 651da177e4SLinus Torvalds 1=excessive nak 6647c51431SJon Mason 2=transmission accepted by the receiver hardware 671da177e4SLinus Torvalds 681da177e4SLinus Torvalds Received packets are also stuffed with the extra 4 bytes but it will 691da177e4SLinus Torvalds be random data. 701da177e4SLinus Torvalds 711da177e4SLinus Torvalds Cap only listens to protocol 1-8. 721da177e4SLinus Torvalds 731da177e4SLinus Torvaldsconfig ARCNET_COM90xx 741da177e4SLinus Torvalds tristate "ARCnet COM90xx (normal) chipset driver" 751da177e4SLinus Torvalds help 761da177e4SLinus Torvalds This is the chipset driver for the standard COM90xx cards. If you 771da177e4SLinus Torvalds have always used the old ARCnet driver without knowing what type of 781da177e4SLinus Torvalds card you had, this is probably the one for you. 791da177e4SLinus Torvalds 8057ce45ddSAdrian Bunk To compile this driver as a module, choose M here. The module will 811da177e4SLinus Torvalds be called com90xx. 821da177e4SLinus Torvalds 831da177e4SLinus Torvaldsconfig ARCNET_COM90xxIO 841da177e4SLinus Torvalds tristate "ARCnet COM90xx (IO mapped) chipset driver" 85*a7f7f624SMasahiro Yamada help 861da177e4SLinus Torvalds This is the chipset driver for the COM90xx cards, using them in 871da177e4SLinus Torvalds IO-mapped mode instead of memory-mapped mode. This is slower than 881da177e4SLinus Torvalds the normal driver. Only use it if your card doesn't support shared 891da177e4SLinus Torvalds memory. 901da177e4SLinus Torvalds 9157ce45ddSAdrian Bunk To compile this driver as a module, choose M here. The module will 921da177e4SLinus Torvalds be called com90io. 931da177e4SLinus Torvalds 941da177e4SLinus Torvaldsconfig ARCNET_RIM_I 951da177e4SLinus Torvalds tristate "ARCnet COM90xx (RIM I) chipset driver" 96*a7f7f624SMasahiro Yamada help 971da177e4SLinus Torvalds This is yet another chipset driver for the COM90xx cards, but this 981da177e4SLinus Torvalds time only using memory-mapped mode, and no IO ports at all. This 991da177e4SLinus Torvalds driver is completely untested, so if you have one of these cards, 1001da177e4SLinus Torvalds please mail <dwmw2@infradead.org>, especially if it works! 1011da177e4SLinus Torvalds 10257ce45ddSAdrian Bunk To compile this driver as a module, choose M here. The module will 1031da177e4SLinus Torvalds be called arc-rimi. 1041da177e4SLinus Torvalds 1051da177e4SLinus Torvaldsconfig ARCNET_COM20020 1061da177e4SLinus Torvalds tristate "ARCnet COM20020 chipset driver" 107754107e3SArnd Bergmann depends on LEDS_CLASS 1081da177e4SLinus Torvalds help 1091da177e4SLinus Torvalds This is the driver for the new COM20020 chipset. It supports such 1101da177e4SLinus Torvalds things as promiscuous mode, so packet sniffing is possible, and 1111da177e4SLinus Torvalds extra diagnostic information. 1121da177e4SLinus Torvalds 11357ce45ddSAdrian Bunk To compile this driver as a module, choose M here. The module will 1141da177e4SLinus Torvalds be called com20020. 1151da177e4SLinus Torvalds 1161da177e4SLinus Torvaldsconfig ARCNET_COM20020_ISA 1171da177e4SLinus Torvalds tristate "Support for COM20020 on ISA" 1181da177e4SLinus Torvalds depends on ARCNET_COM20020 && ISA 1191da177e4SLinus Torvalds 1201da177e4SLinus Torvaldsconfig ARCNET_COM20020_PCI 1211da177e4SLinus Torvalds tristate "Support for COM20020 on PCI" 1221da177e4SLinus Torvalds depends on ARCNET_COM20020 && PCI 1231da177e4SLinus Torvalds 124330278cdSJeff Kirsherconfig ARCNET_COM20020_CS 125330278cdSJeff Kirsher tristate "COM20020 ARCnet PCMCIA support" 126330278cdSJeff Kirsher depends on ARCNET_COM20020 && PCMCIA 127330278cdSJeff Kirsher help 128330278cdSJeff Kirsher Say Y here if you intend to attach this type of ARCnet PCMCIA card 129330278cdSJeff Kirsher to your computer. 130330278cdSJeff Kirsher 131330278cdSJeff Kirsher To compile this driver as a module, choose M here: the module will be 132330278cdSJeff Kirsher called com20020_cs. If unsure, say N. 133330278cdSJeff Kirsher 13442859007SJan Engelhardtendif # ARCNET 135