arch/arm/boot/dts/aspeed/facebook-bmc-flash-layout-128.dtsi
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/aspeed/facebook-bmc-flash-layout-128.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/aspeed/facebook-bmc-flash-layout-128.dtsi- Extension
.dtsi- Size
- 1063 bytes
- Lines
- 61
- 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
- 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+
// Copyright (c) 2020 Facebook Inc.
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
/*
* u-boot partition: 896KB.
*/
u-boot@0 {
reg = <0x0 0xe0000>;
label = "u-boot";
};
/*
* u-boot environment variables: 64KB.
*/
u-boot-env@e0000 {
reg = <0xe0000 0x10000>;
label = "env";
};
/*
* image metadata partition (64KB), used by Facebook internal
* tools.
*/
image-meta@f0000 {
reg = <0xf0000 0x10000>;
label = "meta";
};
/*
* FIT image: 119 MB.
*/
fit@100000 {
reg = <0x100000 0x7700000>;
label = "fit";
};
/*
* "data0" partition (8MB) is used by Facebook BMC platforms as
* persistent data store.
*/
data0@7800000 {
reg = <0x7800000 0x800000>;
label = "data0";
};
/*
* Although the master partition can be created by enabling
* MTD_PARTITIONED_MASTER option, below "flash0" partition is
* explicitly created to avoid breaking legacy applications.
*/
flash0@0 {
reg = <0x0 0x8000000>;
label = "flash0";
};
};
Annotation
- 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.