1.2 KiB
RamBlock
Start with the adaptation procedure for board inputs, source changes, build integration and verification order.
Sparse RAM-backed block storage with optional persistent backing callbacks.
RamBlock publishes the Data image as a block device. Its persistence interface uses native_ufs_store callbacks; the board supplies the storage and reset policy.
Direct mode
With the persistent store open read-write, changed pages live only in the store
window and the seed answers for the rest. Requests run concurrently: reads take
no lock, writes to the same pages never overlap, and a flush waits for the
writes in progress, so every bitmap bit on the medium names a durable page. With
cached store writes the store runs write back (data-fua=1 selects write
through); a synchronize with no write since the last flush sends no command.
Integration
The catalog records implementation scope, hardware and OS requirements, board dependencies, revision, build stage, outputs, and runtime identifiers. The selected profile orders build commands by dependency.
./unixnu build kernel -D /path/to/device