drivers/net/wan/hdlc_raw.c

File Facts

System

Linux kernel

Corpus path

drivers/net/wan/hdlc_raw.c

Extension

.c

Size

2490 bytes

Lines

113

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/errno.h
• linux/hdlc.h
• linux/if_arp.h
• linux/inetdevice.h
• linux/init.h
• linux/kernel.h
• linux/module.h
• linux/pkt_sched.h
• linux/poll.h
• linux/rtnetlink.h
• linux/skbuff.h

Detected Declarations

• function raw_type_trans
• function raw_ioctl
• function hdlc_raw_init
• function hdlc_raw_exit
• module init hdlc_raw_init

Annotated Snippet

module_init(hdlc_raw_init);
module_exit(hdlc_raw_exit);

MODULE_AUTHOR("Krzysztof Halasa <khc@pm.waw.pl>");
MODULE_DESCRIPTION("Raw HDLC protocol support for generic HDLC");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/errno.h`, `linux/hdlc.h`, `linux/if_arp.h`, `linux/inetdevice.h`, `linux/init.h`, `linux/kernel.h`, `linux/module.h`, `linux/pkt_sched.h`.
• Detected declarations: `function raw_type_trans`, `function raw_ioctl`, `function hdlc_raw_init`, `function hdlc_raw_exit`, `module init hdlc_raw_init`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: integration implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.

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.