daniel/danos
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

docs: display v2 design + plan (pluggable scanout backend)

Browse Source 
Keep the GOP framebuffer as the floor, make scanout a pluggable backend, and
upgrade to a native virtio-gpu driver when it announces itself (dynamic
hot-attach; GOP stays the fallback for "no driver ever"). v2 builds the shm
cross-process memory capability, shared with the future client-surface path.
Milestones V1 (backend seam) → V6 (resilience + tests), each with a gate.
This commit is contained in:
Daniel Samson
2026-07-14 09:28:31 +01:00
parent a01a4f3b3d
commit 2723b6f778
3 changed files with 252 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/README.md
+3 -1
View File
@@ -73,7 +73,9 @@ rather than restate it. Roughly in the order things happen at runtime:
track: a user-space compositor that owns the framebuffer, composes a layer stack into
a double buffer, and presents it. Why GOP and the PCI display device are two views of
one controller, the device-node + write-combining handoff, and what flicker-free buys
that tear-free doesn't. Plan: [display-plan.md](display-plan.md).
that tear-free doesn't. Plan: [display-plan.md](display-plan.md). **v2** makes scanout
a pluggable backend (GOP floor + a native virtio-gpu driver, hot-attached):
[display-v2.md](display-v2.md), plan [display-v2-plan.md](display-v2-plan.md).
20. **[halting.md](halting.md) — halting.** Why a kernel can't just "exit", and
how `while (true) hlt` parks the CPU safely once there's nothing left to do.