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

docs: amd-gpus.md — RDNA2 display-driver feasibility, the AMD companion survey

Browse Source
This commit is contained in:
Daniel Samson
2026-07-22 12:25:07 +01:00
parent e63d6ef5ef
commit cacbacd76b
2 changed files with 347 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/README.md
+3 -2
View File
@@ -94,9 +94,10 @@ rather than restate it. Roughly in the order things happen at runtime:
scanout a pluggable backend — GOP floor + a native virtio-gpu driver, hot-attached, with
runtime mode-set, EDID, fenced vsync presents, and restart re-attach:
[display-v2.md](display-v2.md), plan [display-v2-plan.md](display-v2-plan.md). Looking
further out, two research snapshots survey what a *native* driver for real GPU silicon
further out, three research snapshots survey what a *native* driver for real GPU silicon
would take as another `.scanout` backend: [nvidia-gpus.md](nvidia-gpus.md) (RTX 3060 /
Ampere) and [intel-igpu.md](intel-igpu.md) (Intel iGPU).
Ampere), [amd-gpus.md](amd-gpus.md) (RX 6600 / RDNA2), and [intel-igpu.md](intel-igpu.md)
(Intel iGPU).
23. **[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.