drivers/video/nomodeset.c
Source file repositories/reference/linux-study-clean/drivers/video/nomodeset.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/video/nomodeset.c- Extension
.c- Size
- 520 bytes
- Lines
- 27
- 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.
Dependency Surface
linux/module.hlinux/types.hvideo/nomodeset.h
Detected Declarations
function video_firmware_drivers_onlyfunction disable_modesetexport video_firmware_drivers_only
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
#include <linux/module.h>
#include <linux/types.h>
#include <video/nomodeset.h>
static bool video_nomodeset;
bool video_firmware_drivers_only(void)
{
return video_nomodeset;
}
EXPORT_SYMBOL(video_firmware_drivers_only);
static int __init disable_modeset(char *str)
{
video_nomodeset = true;
pr_warn("Booted with the nomodeset parameter. Only the system framebuffer will be available\n");
return 1;
}
/* Disable kernel modesetting */
__setup("nomodeset", disable_modeset);
Annotation
- Immediate include surface: `linux/module.h`, `linux/types.h`, `video/nomodeset.h`.
- Detected declarations: `function video_firmware_drivers_only`, `function disable_modeset`, `export video_firmware_drivers_only`.
- 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.