Daniel Samson
23bcd77c58
Every user binary and the two device-logic library modules (pci, usb) now
`@import` the concern modules directly instead of aliasing through `runtime`:
runtime.ipc/process/time/service/input/block/display -> @import("<module>")
runtime.device / runtime.device_manager -> @import("driver")
runtime.fs -> @import("file-system")
runtime.Thread -> @import("thread").Thread
runtime.system.{write,writeRecord,klog*} -> logging.*
runtime.system.{sleep,timerOnce,wallClock,clock} -> time.*
runtime.system.{spawn*,kill,exit,yield,processes,...}-> process.*
runtime.system.{mmap,munmap,PROT_*} -> memory.*
runtime.dma.* / runtime.shared_memory.* / runtime.allocator -> memory.*
Each consumer keeps its own alias name (e.g. `const device = @import("driver")`),
so call sites are unchanged and there are no collisions with local `driver`
variables. build.zig now injects the concern modules into every user binary via
`default_imports`; pci/usb module import lists were updated to match.
The `runtime` and `system` shims remain for one more step (root.zig still uses
runtime); they are deleted in C5. Nothing but root.zig imports `runtime` now.
Verified: zig build, zig build test, and 17 QEMU cases (smoke, device-manager,
logger, fat-mount, fat-mutations, usb-storage, usb-hid, display-native,
virtio-gpu, input, thread-spawn, thread-mutex, process-kill, shared-memory,
driver-restart, acpi-ps2, pci-scan).
31 lines
1.5 KiB
Zig
31 lines
1.5 KiB
Zig
//! /system/services/fdt — the devicetree discovery service: the ARM twin of the
|
|
//! acpi service (docs/discovery.md — firmware neutrality). **Placeholder: not
|
|
//! implemented.** It exists so the build's `-Ddiscovery` option has both of its
|
|
//! values from day one; the implementation lands with the Raspberry Pi
|
|
//! bring-up (docs/arm.md).
|
|
//!
|
|
//! What it becomes: the per-firmware discoverer for boots that hand over a
|
|
//! flattened device tree instead of ACPI tables. It claims the
|
|
//! `devicetree-blob` node the kernel publishes (the FDT the loader received),
|
|
//! walks the tree — pure data, no bytecode, so unlike the acpi service it
|
|
//! needs no port grant and no interpreter — and, like any bus-shaped driver:
|
|
//! `device_register`s what it finds (containment against the blob node's
|
|
//! recorded apertures), reports each child to the device manager
|
|
//! (`child_added`, identity = the node's `compatible` string), and stays
|
|
//! resident under the manager's supervision (hello, restart, the usual
|
|
//! contract).
|
|
//!
|
|
//! Known prerequisite recorded in docs/discovery.md: `DeviceDescriptor`'s 8-byte `hid`
|
|
//! cannot hold an FDT `compatible` string ("brcm,bcm2835-aux-uart") — identity
|
|
//! widens before this file grows a body.
|
|
|
|
|
|
const process = @import("process");
|
|
pub fn main(init: process.Init) void {
|
|
_ = init;
|
|
// Not implemented: exit cleanly and silently (a bare spawn by the
|
|
// initial-ramdisk sweep must not derange other tests' markers). The
|
|
// supervisor reads a clean exit as "meant to stop" — correct for a
|
|
// placeholder.
|
|
}
|