arch/mips/ralink/prom.c
Source file repositories/reference/linux-study-clean/arch/mips/ralink/prom.c
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/ralink/prom.c- Extension
.c- Size
- 1327 bytes
- Lines
- 66
- 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/string.hasm/bootinfo.hasm/addrspace.hasm/mach-ralink/ralink_regs.hcommon.h
Detected Declarations
function prom_init_cmdlinefunction prom_initexport ralink_soc
Annotated Snippet
if (CPHYSADDR(p) && *p) {
pr_debug("argv[%d]: %s\n", i, p);
strlcat(arcs_cmdline, " ", sizeof(arcs_cmdline));
strlcat(arcs_cmdline, p, sizeof(arcs_cmdline));
}
}
}
void __init prom_init(void)
{
prom_soc_init(&soc_info);
pr_info("SoC Type: %s\n", get_system_type());
prom_init_cmdline();
}
Annotation
- Immediate include surface: `linux/string.h`, `asm/bootinfo.h`, `asm/addrspace.h`, `asm/mach-ralink/ralink_regs.h`, `common.h`.
- Detected declarations: `function prom_init_cmdline`, `function prom_init`, `export ralink_soc`.
- 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.