diff options
Diffstat (limited to 'wiki/Execution-Plane.md')
| -rw-r--r-- | wiki/Execution-Plane.md | 21 |
1 files changed, 13 insertions, 8 deletions
diff --git a/wiki/Execution-Plane.md b/wiki/Execution-Plane.md index 9c6909c..7f6dd6b 100644 --- a/wiki/Execution-Plane.md +++ b/wiki/Execution-Plane.md @@ -8,7 +8,8 @@ > when the two disagree, the docs tree wins. Front door: > [`../docs/README.md`](../docs/README.md). -Status: 2026-11-14, tree `master @ 339da842`. Tags: `[live]` proven with the +Status: 2026-11-15, tree `master @ 444ae2c1` plus in-flight graphics changes in +the working tree. Tags: `[live]` proven with the stock guest driver; `[gated]` implemented, default-off or parameter-gated; `[wip]` partial; `[wall]` current blocker; `[target]` named success latch; `[planned]` designed, not built. @@ -161,14 +162,18 @@ guest: push + QMD + GPFIFO entry + doorbell (BAR0 0x88704) (no method-grammar draw header; the work is macro-driven — data-block blobs plus small state pushes invoking MME macros), the recycled pushes are recovered, and the client's draw-state push opens, captures and reaches the - engine (`GR LAUNCH submitted` + OK, golden MME overlay accepted). No + engine (`GR LAUNCH submitted` + OK, golden MME overlay accepted). The MME + chain now completes and executes the draw macro: multi-frame keep-windows + land, the 2799-word pack completes, the first `MME-PACK-REARM` fires, the + fixed-CB region is aliased, and `DRAW_IAB` (`mac=0x22`) runs with the + SPH-BIND prelude intact (84 words) and the DS stage VAs populated. No non-black **window/screen** frame has been produced through the NVIDIA path - yet: the MME macro program does not complete (the 2799-word packed program - cannot fit its <=2048-word block with the draw window, so `live_gen` never - promotes; the multi-part keep-window A/B is pending), RT routing was tested - and refuted as the cause, glxgears' window is black, and X start keeps a - per-boot first-generation lottery, so those are the named blockers. The - lanes and the ladder are on + yet: the remaining gate is the DS stage-0/1 image (the synthesized binds + read `family+0x900`, zero in the live family page, while the client's VTG + SPH image is at `family+0x600`), so the draw never stores (`wrote=0`, + `px0=0`); the window/screen present is unproven, and the per-boot binding + plus X first-generation lottery is the throughput limiter. Those are the + named blockers. The lanes and the ladder are on [`Graphics-Execution.md`](Graphics-Execution.md). ## 6. Portability |