docs: rename arch.md to architecture.md and update all references
Rename the file to match current naming conventions and update all cross-references throughout the documentation. Update the content to reflect the current state of the codebase: - Module is now called "architecture", not "arch" - Directory is system/kernel/architecture/, not system/kernel/arch/ - Generic kernel file is kernel.zig, not main.zig - Updated file listing for x86_64 architecture module (added smp.zig, per-cpu.zig, ioapic.zig, trampoline.s) - Updated function list in cpu.zig to include enterUser/userExit and address-space management - Clarified that _start lives in architecture-specific isr.s - Expanded architecture-specific vs generic comparison table with actual current modules Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Haiku 4.5
parent
7e4071a065
commit
f9dea7790a
+2
-2
@@ -5,7 +5,7 @@ PCIe config window, the timer, the power registers — in a set of **system
|
||||
description tables** (SDTs). But before it can read any of them, danos has to *find*
|
||||
them, and they aren't at a fixed address. Getting there is a short chain of pointers,
|
||||
and this note explains it — in particular the question it's easy to trip on: **how
|
||||
does the [platform / device module](arch.md) know where the RSDT is?**
|
||||
does the [platform / device module](architecture.md) know where the RSDT is?**
|
||||
|
||||
Short answer: it doesn't receive the RSDT. The firmware hands over the **RSDP**, and
|
||||
the RSDT's address is a field *inside* the RSDP. The platform follows that pointer.
|
||||
@@ -168,5 +168,5 @@ vocabulary, and orderly shutdown — is the power service, [power.md](power.md).
|
||||
ACPI enumeration and events moved to the ring-3 acpi service.
|
||||
- [power.md](power.md) — the domain-named power service the ACPI event side publishes
|
||||
to (button, lid, battery) and its orderly-shutdown path into S5.
|
||||
- [arch.md](arch.md) — why the kernel reaches the device code through a `platform`
|
||||
- [architecture.md](architecture.md) — why the kernel reaches the device code through a `platform`
|
||||
module and never names ACPI directly.
|
||||
|
||||
Reference in New Issue
Block a user