drivers/net/arcnet/capmode.c

File Facts

System

Linux kernel

Corpus path

drivers/net/arcnet/capmode.c

Extension

.c

Size

7656 bytes

Lines

270

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: exported/initcall integration point

Status

integration implementation candidate

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.

• 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/gfp.h
• linux/init.h
• linux/if_arp.h
• net/arp.h
• linux/netdevice.h
• linux/skbuff.h
• arcdevice.h

Detected Declarations

• function rx
• function build_header
• function prepare_tx
• function ack_tx
• function capmode_module_init
• function capmode_module_exit
• module init capmode_module_init

Annotated Snippet

module_init(capmode_module_init);
module_exit(capmode_module_exit);

MODULE_DESCRIPTION("ARCnet CAP mode packet interface module");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/gfp.h`, `linux/init.h`, `linux/if_arp.h`, `net/arp.h`, `linux/netdevice.h`, `linux/skbuff.h`, `arcdevice.h`.
• Detected declarations: `function rx`, `function build_header`, `function prepare_tx`, `function ack_tx`, `function capmode_module_init`, `function capmode_module_exit`, `module init capmode_module_init`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: integration implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.