moving efi code to boot

This commit is contained in:
2026-07-05 10:01:01 +01:00
parent ae1552414d
commit 7c3cffb337
10 changed files with 15 additions and 12 deletions
+1 -1
View File
@@ -66,7 +66,7 @@ the DTB/ACPI tells you what devices exist.
[`MemoryMap`](memory-map.md) — the same neutral handoff `efi.zig` produces, just
from a different source. This is where keeping boot-protocol knowledge on the
loader side (as we did for the UEFI memory-map classification) pays off.
- **The UEFI loader mostly carries over.** `src/efi.zig` is largely
- **The UEFI loader mostly carries over.** `src/boot/efi.zig` is largely
boot-*protocol* code (`std.os.uefi` protocol calls), not x86 code. Its only truly
x86-specific bits are the ELF machine check (`.X86_64`) and the SysV calling
convention for the kernel jump. So an `aarch64`-UEFI target (QEMU `virt` + AAVMF)