arch/powerpc/boot/dts/o2mnt.dts
Source file repositories/reference/linux-study-clean/arch/powerpc/boot/dts/o2mnt.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/powerpc/boot/dts/o2mnt.dts- Extension
.dts- Size
- 517 bytes
- Lines
- 30
- Domain
- Architecture Layer
- Bucket
- arch/powerpc
- Inferred role
- Architecture Layer: configuration, schema, or hardware description
- Status
- atlas-only
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.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-or-later
/*
* O2MNT Device Tree Source
*
* Copyright (C) 2012 DENX Software Engineering
* Anatolij Gustschin <agust@denx.de>
*/
/include/ "o2d.dtsi"
/ {
model = "ifm,o2mnt";
compatible = "ifm,o2d";
localbus {
flash@0,0 {
partition@60000 {
label = "kernel";
reg = <0x00060000 0x00260000>;
read-only;
};
/* add o2mnt specific partitions */
partition@2c0000 {
label = "o2mnt user defined";
reg = <0x002c0000 0x00d40000>;
};
};
};
};
Annotation
- Atlas domain: Architecture Layer / arch/powerpc.
- Implementation status: atlas-only.
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.