drivers/video/fbdev/fm2fb.c
Source file repositories/reference/linux-study-clean/drivers/video/fbdev/fm2fb.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/video/fbdev/fm2fb.c- Extension
.c- Size
- 9173 bytes
- Lines
- 321
- Domain
- Driver Families
- Bucket
- drivers/video
- 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.hlinux/mm.hlinux/fb.hlinux/init.hlinux/zorro.hasm/io.h
Detected Declarations
function fm2fb_blankfunction fm2fb_setcolregfunction fm2fb_probefunction fm2fb_setupfunction fm2fb_initmodule init fm2fb_init
Annotated Snippet
module_init(fm2fb_init);
MODULE_LICENSE("GPL");Annotation
- Immediate include surface: `linux/module.h`, `linux/mm.h`, `linux/fb.h`, `linux/init.h`, `linux/zorro.h`, `asm/io.h`.
- Detected declarations: `function fm2fb_blank`, `function fm2fb_setcolreg`, `function fm2fb_probe`, `function fm2fb_setup`, `function fm2fb_init`, `module init fm2fb_init`.
- Atlas domain: Driver Families / drivers/video.
- 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.