arch/mips/configs/generic/board-boston.config

File Facts

System

Linux kernel

Corpus path

arch/mips/configs/generic/board-boston.config

Extension

.config

Size

682 bytes

Lines

49

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.

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

CONFIG_FIT_IMAGE_FDT_BOSTON=y

CONFIG_ATA=y
CONFIG_SATA_AHCI=y
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y

CONFIG_AUXDISPLAY=y
CONFIG_IMG_ASCII_LCD=y

CONFIG_COMMON_CLK_BOSTON=y

CONFIG_DMADEVICES=y
CONFIG_PCH_DMA=y

CONFIG_GPIOLIB=y
CONFIG_GPIO_SYSFS=y
CONFIG_GPIO_PCH=y

CONFIG_I2C=y
CONFIG_I2C_EG20T=y

CONFIG_MMC=y
CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_PCI=y

CONFIG_NETDEVICES=y
CONFIG_PCH_GBE=y

CONFIG_PCI=y
CONFIG_PCI_MSI=y
CONFIG_PCIE_XILINX=y

CONFIG_PCH_PHUB=y

CONFIG_RTC_CLASS=y
CONFIG_RTC_DRV_M41T80=y

CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_OF_PLATFORM=y

CONFIG_SPI=y
CONFIG_SPI_TOPCLIFF_PCH=y

CONFIG_USB=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_OHCI_HCD=y

Annotation

• Atlas domain: Architecture Layer / arch/mips.
• Implementation status: atlas-only.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.