drivers/net/arcnet/Kconfig

Source file repositories/reference/linux-study-clean/drivers/net/arcnet/Kconfig

File Facts

System
Linux kernel
Corpus path
drivers/net/arcnet/Kconfig
Extension
[no extension]
Size
3117 bytes
Lines
87
Domain
Driver Families
Bucket
drivers/net
Inferred role
Driver Families: build/configuration rule
Status
atlas-only

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Dependency Surface

Detected Declarations

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
#
# Arcnet configuration
#

menuconfig ARCNET
	depends on NETDEVICES && PCI && HAS_IOPORT
	tristate "ARCnet support"
	help
	  If you have a network card of this type, say Y and check out the
	  (arguably) beautiful poetry in
	  <file:Documentation/networking/arcnet.rst>.

	  You need both this driver, and the driver for the particular ARCnet
	  chipset of your card.

	  To compile this driver as a module, choose M here. The module will
	  be called arcnet.

if ARCNET

config ARCNET_1201
	tristate "Enable standard ARCNet packet format (RFC 1201)"
	help
	  This allows you to use RFC1201 with your ARCnet card via the virtual
	  arc0 device.  You need to say Y here to communicate with
	  industry-standard RFC1201 implementations, like the arcether.com
	  packet driver or most DOS/Windows ODI drivers.  Please read the
	  ARCnet documentation in <file:Documentation/networking/arcnet.rst>
	  for more information about using arc0.

config ARCNET_1051
	tristate "Enable old ARCNet packet format (RFC 1051)"
	help
	  This allows you to use RFC1051 with your ARCnet card via the virtual
	  arc0s device. You only need arc0s if you want to talk to ARCnet
	  software complying with the "old" standard, specifically, the DOS
	  arcnet.com packet driver, Amigas running AmiTCP, and some variants
	  of NetBSD. You do not need to say Y here to communicate with
	  industry-standard RFC1201 implementations, like the arcether.com
	  packet driver or most DOS/Windows ODI drivers. RFC1201 is included
	  automatically as the arc0 device. Please read the ARCnet
	  documentation in <file:Documentation/networking/arcnet.rst> for more
	  information about using arc0e and arc0s.

config ARCNET_RAW
	tristate "Enable raw mode packet interface"
	help
	  ARCnet "raw mode" packet encapsulation, no soft headers.  Unlikely
	  to work unless talking to a copy of the same Linux arcnet driver,
	  but perhaps marginally faster in that case.

config ARCNET_CAP
	tristate "Enable CAP mode packet interface"
	help
	  ARCnet "cap mode" packet encapsulation. Used to get the hardware
	  acknowledge back to userspace. After the initial protocol byte every
	  packet is stuffed with an extra 4 byte "cookie" which doesn't
	  actually appear on the network. After transmit the driver will send
	  back a packet with protocol byte 0 containing the status of the
	  transmission:
	     0=no hardware acknowledge
	     1=excessive nak
	     2=transmission accepted by the receiver hardware

	  Received packets are also stuffed with the extra 4 bytes but it will
	  be random data.

	  Cap only listens to protocol 1-8.

Annotation

Implementation Notes