drivers/video/fbdev/sunxvr2500.c

File Facts

System

Linux kernel

Corpus path

drivers/video/fbdev/sunxvr2500.c

Extension

.c

Size

5352 bytes

Lines

251

Domain

Driver Families

Bucket

drivers/video

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/aperture.h
• linux/kernel.h
• linux/fb.h
• linux/pci.h
• linux/init.h
• linux/of.h
• asm/io.h

Detected Declarations

• struct s3d_info
• function s3d_get_props
• function s3d_setcolreg
• function s3d_set_fbinfo
• function s3d_pci_register
• function s3d_init
• module init s3d_init

Annotated Snippet

static struct pci_driver s3d_driver = {
	.driver = {
		.suppress_bind_attrs = true,
	},
	.name		= "s3d",
	.id_table	= s3d_pci_table,
	.probe		= s3d_pci_register,
};

static int __init s3d_init(void)
{
	if (fb_modesetting_disabled("s3d"))
		return -ENODEV;

	if (fb_get_options("s3d", NULL))
		return -ENODEV;

	return pci_register_driver(&s3d_driver);
}
device_initcall(s3d_init);

Annotation

• Immediate include surface: `linux/aperture.h`, `linux/kernel.h`, `linux/fb.h`, `linux/pci.h`, `linux/init.h`, `linux/of.h`, `asm/io.h`.
• Detected declarations: `struct s3d_info`, `function s3d_get_props`, `function s3d_setcolreg`, `function s3d_set_fbinfo`, `function s3d_pci_register`, `function s3d_init`, `module init s3d_init`.
• Atlas domain: Driver Families / drivers/video.
• Implementation status: pattern 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.