arch/mips/sibyte/Platform

Source file repositories/reference/linux-study-clean/arch/mips/sibyte/Platform

File Facts

System: Linux kernel
Corpus path: arch/mips/sibyte/Platform
Extension: [no extension]
Size: 1043 bytes
Lines: 33
Domain: Architecture Layer
Bucket: arch/mips
Inferred role: Architecture Layer: arch/mips
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

#
# These are all rather similar so we consider them a single platform
#

#
# Sibyte SB1250 / BCM1480 family of SOCs
#
cflags-$(CONFIG_SIBYTE_BCM112X) +=					\
		-I$(srctree)/arch/mips/include/asm/mach-sibyte		\
		-DSIBYTE_HDR_FEATURES=SIBYTE_HDR_FMASK_1250_112x_ALL

cflags-$(CONFIG_SIBYTE_SB1250)	+=					\
		-I$(srctree)/arch/mips/include/asm/mach-sibyte		\
		-DSIBYTE_HDR_FEATURES=SIBYTE_HDR_FMASK_1250_112x_ALL

cflags-$(CONFIG_SIBYTE_BCM1x80) +=					\
		-I$(srctree)/arch/mips/include/asm/mach-sibyte		\
		-DSIBYTE_HDR_FEATURES=SIBYTE_HDR_FMASK_1480_ALL

#
# Sibyte BCM91125C (CRhone) board
# Sibyte BCM91125E (Rhone) board
# Sibyte BCM91250A (SWARM) board
# Sibyte BCM91250C2 (LittleSur) board
# Sibyte BCM91x80 (BigSur) board
#
load-$(CONFIG_SIBYTE_CRHONE)	:= 0xffffffff80100000
load-$(CONFIG_SIBYTE_RHONE)	:= 0xffffffff80100000
load-$(CONFIG_SIBYTE_SENTOSA)	:= 0xffffffff80100000
load-$(CONFIG_SIBYTE_SWARM)	:= 0xffffffff80100000
load-$(CONFIG_SIBYTE_BIGSUR)	:= 0xffffffff80100000
load-$(CONFIG_SIBYTE_LITTLESUR) := 0xffffffff80100000

Annotation

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.