arch/mips/boot/dts/ralink/vocore2.dts

File Facts

System

Linux kernel

Corpus path

arch/mips/boot/dts/ralink/vocore2.dts

Extension

.dts

Size

261 bytes

Lines

19

Domain

Architecture Layer

Bucket

arch/mips

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

• mt7628a.dtsi

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

/dts-v1/;

#include "mt7628a.dtsi"

/ {
	compatible = "vocore,vocore2", "ralink,mt7628a-soc";
	model = "VoCore2";

	memory@0 {
		device_type = "memory";
		reg = <0x0 0x8000000>;
	};

	chosen {
		bootargs = "console=ttyS2,115200";
		stdout-path = &uart2;
	};
};

Annotation

• Immediate include surface: `mt7628a.dtsi`.
• Atlas domain: Architecture Layer / arch/mips.
• 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.