system/services/acpi and system/services/fdt exist as documented placeholders (silent clean-exit mains; the headers say exactly what each becomes and why). The build's -Ddiscovery=acpi|fdt option fills the ramdisk's neutral 'discovery' slot — the device manager will spawn "discovery" by that name in M20.3 and never learn which firmware it is on (m19-m20-plan.md decision 7). x86 defaults to acpi; the aarch64 target flips the default when it lands. |
||
|---|---|---|
| .. | ||
| fdt.zig | ||