summaryrefslogtreecommitdiffstats
path: root/wiki/System-Overview.md
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/System-Overview.md')
-rw-r--r--wiki/System-Overview.md25
1 files changed, 15 insertions, 10 deletions
diff --git a/wiki/System-Overview.md b/wiki/System-Overview.md
index aeefb46..74adf71 100644
--- a/wiki/System-Overview.md
+++ b/wiki/System-Overview.md
@@ -7,7 +7,8 @@
> and [`../docs/03-architecture/10-interaction-and-scheduling.md`](../docs/03-architecture/10-interaction-and-scheduling.md)
> for the full picture); the docs tree wins on disagreement.
-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; `[wip]` partial;
`[wall]` current blocker; `[target]` designed end state.
@@ -152,15 +153,19 @@ RPC from the guest to "firmware":
client push carries a 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 with the golden MME overlay. The wall is
- MME macro completion: the 2799-word packed program cannot fit its
- <=2048-word block with the draw window, so `live_gen` never promotes and
- the draw never stores (RT routing was tested and refuted; the multi-part
- keep-window A/B is pending). The window/screen present is unproven
- (a window draw can wedge X and glxgears' window is black), and X start
- keeps a first-generation lottery (the dominant throughput limiter), so the
- remaining gate is the macro completion plus the window/screen present
- before the first non-black window frame
+ captures and reaches the engine with the golden MME overlay. 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 and the DS stage VAs populated. 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 (a window draw can wedge X and glxgears'
+ window is black), and the per-boot binding plus X first-generation start
+ lottery is the dominant throughput limiter, so the remaining gate is the
+ DS stage image plus the window/screen present before the first non-black
+ window frame
([`OpenGL.md`](OpenGL.md), [`Vulkan.md`](Vulkan.md)).
## 6. Where the detail lives