documenting research for arm and device discovery

This commit is contained in:
2026-07-03 20:22:48 +01:00
parent 99d6bf5ce3
commit f9f0511ac2
3 changed files with 293 additions and 0 deletions
+6
View File
@@ -51,6 +51,12 @@ Cutting across all of these:
- **[arch.md](arch.md) — the architecture split.** How CPU-specific code is kept
behind a build-time `arch` module so the generic kernel never names x86_64,
leaving room for other systems (e.g. an AArch64 Raspberry Pi) later.
- **[arm.md](arm.md) — ARM targets.** The Raspberry Pi landscape the arch split is
aiming at: `arm` (32-bit, Pi Zero W) vs `aarch64` (64-bit, Pi 3-5), UEFI vs
device-tree boot, and what each layer needs.
- **[discovery.md](discovery.md) — device discovery.** A design note (not built yet)
on learning what hardware exists via ACPI (x86) or device tree (ARM) behind one
neutral device model — when to build it, and how to keep it architecture-agnostic.
- **[sysv.md](sysv.md) — the calling convention.** What "the kernel is SysV" means,
and why the loader→kernel boundary has to pin it (the RDI-vs-RCX handoff).
- **[testing.md](testing.md) — testing.** How the kernel is tested by booting it in