arch/m68k/hp300/README.hp300
Source file repositories/reference/linux-study-clean/arch/m68k/hp300/README.hp300
File Facts
- System
- Linux kernel
- Corpus path
arch/m68k/hp300/README.hp300- Extension
.hp300- Size
- 501 bytes
- Lines
- 15
- Domain
- Architecture Layer
- Bucket
- arch/m68k
- Inferred role
- Architecture Layer: arch/m68k
- 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
HP300 notes
-----------
The Linux/HP web page is at <http://www.tazenda.demon.co.uk/phil/linux-hp/>
Currently only 9000/340 machines have been tested. Any amount of RAM should
work now but I've only tried 16MB and 12MB.
The serial console is probably broken at the moment but the Topcat/HIL keyboard
combination seems to work for me. Your mileage may vary.
The LANCE driver works after a fashion but only if you reset the chip before
every packet. This doesn't make for very speedy operation.Annotation
- Atlas domain: Architecture Layer / arch/m68k.
- 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.