arch/mips/ralink/bootrom.c
Source file repositories/reference/linux-study-clean/arch/mips/ralink/bootrom.c
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/ralink/bootrom.c- Extension
.c- Size
- 600 bytes
- Lines
- 30
- Domain
- Architecture Layer
- Bucket
- arch/mips
- Inferred role
- Architecture Layer: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- 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/debugfs.hlinux/seq_file.h
Detected Declarations
function bootrom_showfunction bootrom_setup
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
*
* Copyright (C) 2013 John Crispin <john@phrozen.org>
*/
#include <linux/debugfs.h>
#include <linux/seq_file.h>
#define BOOTROM_OFFSET 0x10118000
#define BOOTROM_SIZE 0x8000
static void __iomem *membase = (void __iomem *) KSEG1ADDR(BOOTROM_OFFSET);
static int bootrom_show(struct seq_file *s, void *unused)
{
seq_write(s, membase, BOOTROM_SIZE);
return 0;
}
DEFINE_SHOW_ATTRIBUTE(bootrom);
static int __init bootrom_setup(void)
{
debugfs_create_file("bootrom", 0444, NULL, NULL, &bootrom_fops);
return 0;
}
postcore_initcall(bootrom_setup);
Annotation
- Immediate include surface: `linux/debugfs.h`, `linux/seq_file.h`.
- Detected declarations: `function bootrom_show`, `function bootrom_setup`.
- Atlas domain: Architecture Layer / arch/mips.
- 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.