arch/arm/boot/dts/broadcom/bcm7445-bcm97445svmb.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/broadcom/bcm7445-bcm97445svmb.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/broadcom/bcm7445-bcm97445svmb.dts- Extension
.dts- Size
- 714 bytes
- Lines
- 39
- Domain
- Architecture Layer
- Bucket
- arch/arm
- 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
bcm7445.dtsi
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/dts-v1/;
#include "bcm7445.dtsi"
/ {
model = "Broadcom STB (bcm7445), SVMB reference board";
compatible = "brcm,bcm7445", "brcm,brcmstb";
memory@0 {
device_type = "memory";
reg = <0x00 0x00000000 0x00 0x40000000>,
<0x00 0x40000000 0x00 0x40000000>,
<0x00 0x80000000 0x00 0x40000000>;
};
};
&nand_controller {
status = "okay";
nand@1 {
compatible = "brcm,nandcs";
reg = <1>;
nand-ecc-step-size = <512>;
nand-ecc-strength = <8>;
nand-on-flash-bbt;
#size-cells = <2>;
#address-cells = <2>;
flash1.rootfs0@0 {
reg = <0x0 0x0 0x0 0x80000000>;
};
flash1.rootfs1@80000000 {
reg = <0x0 0x80000000 0x0 0x80000000>;
};
};
};
Annotation
- Immediate include surface: `bcm7445.dtsi`.
- Atlas domain: Architecture Layer / arch/arm.
- 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.