arch/m68k/include/asm/sun3x.h

Source file repositories/reference/linux-study-clean/arch/m68k/include/asm/sun3x.h

File Facts

System: Linux kernel
Corpus path: arch/m68k/include/asm/sun3x.h
Extension: .h
Size: 868 bytes
Lines: 29
Domain: Architecture Layer
Bucket: arch/m68k
Inferred role: Architecture Layer: implementation source
Status: source implementation candidate

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

#ifndef SUN3X_H
#define SUN3X_H

/* hardware addresses */
#define SUN3X_IOMMU       0x60000000
#define SUN3X_ENAREG      0x61000000
#define SUN3X_INTREG      0x61001400
#define SUN3X_DIAGREG     0x61001800
#define SUN3X_ZS1         0x62000000
#define SUN3X_ZS2         0x62002000
#define SUN3X_LANCE       0x65002000
#define SUN3X_EEPROM      0x64000000
#define SUN3X_IDPROM      0x640007d8
#define SUN3X_VIDEO_BASE  0x50000000
#define SUN3X_VIDEO_P4ID  0x50300000
#define SUN3X_ESP_BASE	  0x66000000
#define SUN3X_ESP_DMA	  0x66001000
#define SUN3X_FDC         0x6e000000
#define SUN3X_FDC_FCR     0x6e000400
#define SUN3X_FDC_FVR     0x6e000800

/* some NVRAM addresses */
#define SUN3X_EEPROM_CONS	(SUN3X_EEPROM + 0x1f)
#define SUN3X_EEPROM_PORTA	(SUN3X_EEPROM + 0x58)
#define SUN3X_EEPROM_PORTB	(SUN3X_EEPROM + 0x60)

#endif

Annotation

Atlas domain: Architecture Layer / arch/m68k.
Implementation status: source implementation candidate.

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.