1ec8f24b7SThomas Gleixner# SPDX-License-Identifier: GPL-2.0-only 21da177e4SLinus Torvalds# 31da177e4SLinus Torvalds# Arcnet configuration 41da177e4SLinus Torvalds# 51da177e4SLinus Torvalds 642859007SJan Engelhardtmenuconfig ARCNET 7*910394c7SEthan Nelson-Moore depends on NETDEVICES && PCI && HAS_IOPORT 8fc0b927dSBen Hutchings tristate "ARCnet support" 9a7f7f624SMasahiro 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 15*910394c7SEthan Nelson-Moore chipset of your card. 161da177e4SLinus Torvalds 1757ce45ddSAdrian Bunk To compile this driver as a module, choose M here. The module will 181da177e4SLinus Torvalds be called arcnet. 191da177e4SLinus Torvalds 2042859007SJan Engelhardtif ARCNET 2142859007SJan Engelhardt 221da177e4SLinus Torvaldsconfig ARCNET_1201 231da177e4SLinus Torvalds tristate "Enable standard ARCNet packet format (RFC 1201)" 241da177e4SLinus Torvalds help 251da177e4SLinus Torvalds This allows you to use RFC1201 with your ARCnet card via the virtual 261da177e4SLinus Torvalds arc0 device. You need to say Y here to communicate with 271da177e4SLinus Torvalds industry-standard RFC1201 implementations, like the arcether.com 281da177e4SLinus Torvalds packet driver or most DOS/Windows ODI drivers. Please read the 2908bab46fSMauro Carvalho Chehab ARCnet documentation in <file:Documentation/networking/arcnet.rst> 301da177e4SLinus Torvalds for more information about using arc0. 311da177e4SLinus Torvalds 321da177e4SLinus Torvaldsconfig ARCNET_1051 331da177e4SLinus Torvalds tristate "Enable old ARCNet packet format (RFC 1051)" 34a7f7f624SMasahiro Yamada help 351da177e4SLinus Torvalds This allows you to use RFC1051 with your ARCnet card via the virtual 361da177e4SLinus Torvalds arc0s device. You only need arc0s if you want to talk to ARCnet 371da177e4SLinus Torvalds software complying with the "old" standard, specifically, the DOS 381da177e4SLinus Torvalds arcnet.com packet driver, Amigas running AmiTCP, and some variants 391da177e4SLinus Torvalds of NetBSD. You do not need to say Y here to communicate with 401da177e4SLinus Torvalds industry-standard RFC1201 implementations, like the arcether.com 411da177e4SLinus Torvalds packet driver or most DOS/Windows ODI drivers. RFC1201 is included 421da177e4SLinus Torvalds automatically as the arc0 device. Please read the ARCnet 4308bab46fSMauro Carvalho Chehab documentation in <file:Documentation/networking/arcnet.rst> for more 441da177e4SLinus Torvalds information about using arc0e and arc0s. 451da177e4SLinus Torvalds 461da177e4SLinus Torvaldsconfig ARCNET_RAW 471da177e4SLinus Torvalds tristate "Enable raw mode packet interface" 481da177e4SLinus Torvalds help 491da177e4SLinus Torvalds ARCnet "raw mode" packet encapsulation, no soft headers. Unlikely 501da177e4SLinus Torvalds to work unless talking to a copy of the same Linux arcnet driver, 511da177e4SLinus Torvalds but perhaps marginally faster in that case. 521da177e4SLinus Torvalds 531da177e4SLinus Torvaldsconfig ARCNET_CAP 541da177e4SLinus Torvalds tristate "Enable CAP mode packet interface" 551da177e4SLinus Torvalds help 561da177e4SLinus Torvalds ARCnet "cap mode" packet encapsulation. Used to get the hardware 571da177e4SLinus Torvalds acknowledge back to userspace. After the initial protocol byte every 581da177e4SLinus Torvalds packet is stuffed with an extra 4 byte "cookie" which doesn't 591da177e4SLinus Torvalds actually appear on the network. After transmit the driver will send 601da177e4SLinus Torvalds back a packet with protocol byte 0 containing the status of the 6147c51431SJon Mason transmission: 621da177e4SLinus Torvalds 0=no hardware acknowledge 631da177e4SLinus Torvalds 1=excessive nak 6447c51431SJon Mason 2=transmission accepted by the receiver hardware 651da177e4SLinus Torvalds 661da177e4SLinus Torvalds Received packets are also stuffed with the extra 4 bytes but it will 671da177e4SLinus Torvalds be random data. 681da177e4SLinus Torvalds 691da177e4SLinus Torvalds Cap only listens to protocol 1-8. 701da177e4SLinus Torvalds 711da177e4SLinus Torvaldsconfig ARCNET_COM20020 721da177e4SLinus Torvalds tristate "ARCnet COM20020 chipset driver" 73754107e3SArnd Bergmann depends on LEDS_CLASS 741da177e4SLinus Torvalds help 751da177e4SLinus Torvalds This is the driver for the new COM20020 chipset. It supports such 761da177e4SLinus Torvalds things as promiscuous mode, so packet sniffing is possible, and 771da177e4SLinus Torvalds extra diagnostic information. 781da177e4SLinus Torvalds 7957ce45ddSAdrian Bunk To compile this driver as a module, choose M here. The module will 801da177e4SLinus Torvalds be called com20020. 811da177e4SLinus Torvalds 821da177e4SLinus Torvaldsconfig ARCNET_COM20020_PCI 831da177e4SLinus Torvalds tristate "Support for COM20020 on PCI" 841da177e4SLinus Torvalds depends on ARCNET_COM20020 && PCI 851da177e4SLinus Torvalds 8642859007SJan Engelhardtendif # ARCNET 87