diff options
Diffstat (limited to 'wiki/FAQ.md')
| -rw-r--r-- | wiki/FAQ.md | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/wiki/FAQ.md b/wiki/FAQ.md index b527ce2..7c7a0a0 100644 --- a/wiki/FAQ.md +++ b/wiki/FAQ.md @@ -5,7 +5,7 @@ > [`../docs/09-reference/glossary-and-faq.md`](../docs/09-reference/glossary-and-faq.md); > the docs tree wins on disagreement. -Status: 2026-11-15, tree `master @ 6aeb20c7`. +Status: 2026-11-15, tree `master @ 88d5005a`. ## Project and positioning @@ -62,13 +62,16 @@ populated. The DS stage-0/1 image is now authored and live: a VTG SPH at (reproduced on two boots). The release path is now host-deterministic when the pack completes (the saved-window release carrier replays the held window with the calls released; the held-CALL census plus the SA[34] golden fill -prove `client=golden=used=0x265`). Window and screen pixels are still the -wall: the blocker is call order (the 728-B window places the slot-34 -`DRAW_IAB` call after the `0x33/0x39` setup, so the `0x39` DS latch -`0x84000420` pre-empts it; the 324-B window places it first and ran -`mac=0x22`), the reorder `a03a68ea` is landed but unexercised, pack -completion is still a per-boot lottery, the DS stage type/context bits -(SPH5/SPH10/SPH18) remain, so the draw never stores, glxgears' window is +prove `client=golden=used=0x265`). **The draw macro now executes end to +end**: c788 ran `DRAW_IAB` (`mac=0x22`) on a released held window after the +`MME-DRAW-MOVE` reorder, TCS-off clears the DS latch (the `0x84000420` was +the synthesized TCS bind), a synthetic viewport and a chained release +complete the replay, and the body decodes with the public Mesa MME toolchain +(8 draws of 3 vertices). Window and screen pixels are still the wall: the +remaining blockers are the vertex buffer (no captured client push binds the +stream; the eng71 scan candidate is a heuristic) and render-target +store/alias visibility (the big-surface alias pages do not yet enter the +write-witness set), so the draw never stores, glxgears' window is black, and the per-boot binding plus X first-generation start lottery is the throughput limiter. The guest Vulkan pipeline runs end to end (device |
