11da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds# 21da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds# Arcnet configuration 31da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds# 41da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 542859007f458f305624009862d6ca818e3c5be57Jan Engelhardtmenuconfig ARCNET 6330278cde612888e79fc4ab13d8f725258e903ddJeff Kirsher depends on NETDEVICES && (ISA || PCI || PCMCIA) 7fc0b927d9a5024e138c4318fe19a590f23e3eeecBen Hutchings tristate "ARCnet support" 81da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds ---help--- 91da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If you have a network card of this type, say Y and check out the 101da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds (arguably) beautiful poetry in 111da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds <file:Documentation/networking/arcnet.txt>. 121da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 131da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds You need both this driver, and the driver for the particular ARCnet 141da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds chipset of your card. If you don't know, then it's probably a 151da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset 161da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds support" below. 171da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 181da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds You might also want to have a look at the Ethernet-HOWTO, available 191da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds from <http://www.tldp.org/docs.html#howto>(even though ARCnet 201da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds is not really Ethernet). 211da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 2257ce45dd16cd427ac2bdef202daf513bd25d650bAdrian Bunk To compile this driver as a module, choose M here. The module will 231da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds be called arcnet. 241da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 2542859007f458f305624009862d6ca818e3c5be57Jan Engelhardtif ARCNET 2642859007f458f305624009862d6ca818e3c5be57Jan Engelhardt 271da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig ARCNET_1201 281da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds tristate "Enable standard ARCNet packet format (RFC 1201)" 291da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 301da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds This allows you to use RFC1201 with your ARCnet card via the virtual 311da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds arc0 device. You need to say Y here to communicate with 321da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds industry-standard RFC1201 implementations, like the arcether.com 331da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds packet driver or most DOS/Windows ODI drivers. Please read the 341da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds ARCnet documentation in <file:Documentation/networking/arcnet.txt> 351da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds for more information about using arc0. 361da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 371da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig ARCNET_1051 381da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds tristate "Enable old ARCNet packet format (RFC 1051)" 391da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds ---help--- 401da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds This allows you to use RFC1051 with your ARCnet card via the virtual 411da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds arc0s device. You only need arc0s if you want to talk to ARCnet 421da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds software complying with the "old" standard, specifically, the DOS 431da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds arcnet.com packet driver, Amigas running AmiTCP, and some variants 441da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds of NetBSD. You do not need to say Y here to communicate with 451da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds industry-standard RFC1201 implementations, like the arcether.com 461da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds packet driver or most DOS/Windows ODI drivers. RFC1201 is included 471da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds automatically as the arc0 device. Please read the ARCnet 481da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds documentation in <file:Documentation/networking/arcnet.txt> for more 491da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds information about using arc0e and arc0s. 501da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 511da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig ARCNET_RAW 521da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds tristate "Enable raw mode packet interface" 531da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 541da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds ARCnet "raw mode" packet encapsulation, no soft headers. Unlikely 551da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds to work unless talking to a copy of the same Linux arcnet driver, 561da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds but perhaps marginally faster in that case. 571da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 581da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig ARCNET_CAP 591da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds tristate "Enable CAP mode packet interface" 601da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 611da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds ARCnet "cap mode" packet encapsulation. Used to get the hardware 621da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds acknowledge back to userspace. After the initial protocol byte every 631da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds packet is stuffed with an extra 4 byte "cookie" which doesn't 641da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds actually appear on the network. After transmit the driver will send 651da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds back a packet with protocol byte 0 containing the status of the 6647c51431fcc5fce3108e8e549cc9d243acd462edJon Mason transmission: 671da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 0=no hardware acknowledge 681da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 1=excessive nak 6947c51431fcc5fce3108e8e549cc9d243acd462edJon Mason 2=transmission accepted by the receiver hardware 701da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 711da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Received packets are also stuffed with the extra 4 bytes but it will 721da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds be random data. 731da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 741da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Cap only listens to protocol 1-8. 751da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 761da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig ARCNET_COM90xx 771da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds tristate "ARCnet COM90xx (normal) chipset driver" 781da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 791da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds This is the chipset driver for the standard COM90xx cards. If you 801da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds have always used the old ARCnet driver without knowing what type of 811da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds card you had, this is probably the one for you. 821da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 8357ce45dd16cd427ac2bdef202daf513bd25d650bAdrian Bunk To compile this driver as a module, choose M here. The module will 841da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds be called com90xx. 851da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 861da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig ARCNET_COM90xxIO 871da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds tristate "ARCnet COM90xx (IO mapped) chipset driver" 881da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds ---help--- 891da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds This is the chipset driver for the COM90xx cards, using them in 901da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds IO-mapped mode instead of memory-mapped mode. This is slower than 911da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds the normal driver. Only use it if your card doesn't support shared 921da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds memory. 931da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 9457ce45dd16cd427ac2bdef202daf513bd25d650bAdrian Bunk To compile this driver as a module, choose M here. The module will 951da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds be called com90io. 961da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 971da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig ARCNET_RIM_I 981da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds tristate "ARCnet COM90xx (RIM I) chipset driver" 991da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds ---help--- 1001da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds This is yet another chipset driver for the COM90xx cards, but this 1011da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds time only using memory-mapped mode, and no IO ports at all. This 1021da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds driver is completely untested, so if you have one of these cards, 1031da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds please mail <dwmw2@infradead.org>, especially if it works! 1041da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 10557ce45dd16cd427ac2bdef202daf513bd25d650bAdrian Bunk To compile this driver as a module, choose M here. The module will 1061da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds be called arc-rimi. 1071da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 1081da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig ARCNET_COM20020 1091da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds tristate "ARCnet COM20020 chipset driver" 1101da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 1111da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds This is the driver for the new COM20020 chipset. It supports such 1121da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds things as promiscuous mode, so packet sniffing is possible, and 1131da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds extra diagnostic information. 1141da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 11557ce45dd16cd427ac2bdef202daf513bd25d650bAdrian Bunk To compile this driver as a module, choose M here. The module will 1161da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds be called com20020. 1171da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 1181da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig ARCNET_COM20020_ISA 1191da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds tristate "Support for COM20020 on ISA" 1201da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on ARCNET_COM20020 && ISA 1211da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 1221da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig ARCNET_COM20020_PCI 1231da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds tristate "Support for COM20020 on PCI" 1241da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on ARCNET_COM20020 && PCI 1251da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 126330278cde612888e79fc4ab13d8f725258e903ddJeff Kirsherconfig ARCNET_COM20020_CS 127330278cde612888e79fc4ab13d8f725258e903ddJeff Kirsher tristate "COM20020 ARCnet PCMCIA support" 128330278cde612888e79fc4ab13d8f725258e903ddJeff Kirsher depends on ARCNET_COM20020 && PCMCIA 129330278cde612888e79fc4ab13d8f725258e903ddJeff Kirsher help 130330278cde612888e79fc4ab13d8f725258e903ddJeff Kirsher Say Y here if you intend to attach this type of ARCnet PCMCIA card 131330278cde612888e79fc4ab13d8f725258e903ddJeff Kirsher to your computer. 132330278cde612888e79fc4ab13d8f725258e903ddJeff Kirsher 133330278cde612888e79fc4ab13d8f725258e903ddJeff Kirsher To compile this driver as a module, choose M here: the module will be 134330278cde612888e79fc4ab13d8f725258e903ddJeff Kirsher called com20020_cs. If unsure, say N. 135330278cde612888e79fc4ab13d8f725258e903ddJeff Kirsher 13642859007f458f305624009862d6ca818e3c5be57Jan Engelhardtendif # ARCNET 137