CONFIG_ARCNET_CAP: Enable CAP mode packet interface

General informations

The Linux kernel configuration item CONFIG_ARCNET_CAP:

• prompt: Enable CAP mode packet interface
• type: tristate
• depends on: (none)
• defined in drivers/net/arcnet/Kconfig
• found in Linux kernels: 2.6.11–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12, 6.13-rc+HEAD
• modules built: capmode

Help text

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.

Hardware

LKDDb

Raw data from LKDDb:

• lkddb module capmode CONFIG_ARCNET_CAP : drivers/net/arcnet/Kconfig : "Enable CAP mode packet interface" # in 2.6.11–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12, 6.13-rc+HEAD

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: