summaryrefslogtreecommitdiff
path: root/examples/rf.zig
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-08-25 21:39:03 -0300
committerGabriel Schneider <[email protected]>2026-08-25 21:40:14 -0300
commit6bb2023a419e56a50cd40fb407abd9dda250d088 (patch)
tree2716adb3732a6edd0858cd4a90242da173b50c12 /examples/rf.zig
parentaa524eae414f4875794638df0586c011c6b0f2c5 (diff)
downloadesp32p4-6bb2023a419e56a50cd40fb407abd9dda250d088.tar.gz
esp32p4-6bb2023a419e56a50cd40fb407abd9dda250d088.zip
Report: the clock, the renderer, and a minimum frame owned by the USB bridge
Brings the document up to the end of Experiment 4. Two rows on the progression table - 360 MHz and direct emission - plus the sections behind them, the corrected verifier, and a summary that no longer says the target was missed. It is met: 3.74 ms from 16.99. The two findings worth more than the number, and both are written up as findings rather than as steps: A 4x clock bought 2.6x. The grid walk reads 27 KB a frame at about six cycles a byte, so it is bounded by L2MEM bandwidth and does not care how fast the core runs. Predicted before the measurement. The direct renderer measured SLOWER at first - less computation, a quarter of the bytes, worse round trip - because the CH340 forwards a bulk IN packet only when the packet is full, and a 21-byte frame does not fill 32. It waits about a millisecond for a timer. So the frame has a minimum size and it belongs to the transport, not the terminal; the emitter pads to it with repeated cursor positioning. The table of 21/49/81-byte frames is in the report because the MINIMUM column is the tell: the small frame's floor was already 530 us below vaxis's, exactly the compute saved, and only the median was hostage. Also corrected: the verifier section. It described hashing SGR parameters per cell, which is a history rather than a state, and that version reported a difference on the die that did not exist - a faster board split the same keystrokes across different frames and reached the same colours by another route. The document now says what it does instead, and why the from-scratch renderer could not have been verified without the fix. Table 13, the ranked recommendations from Experiment 3, is kept as the prediction it was with a note on what has since been applied and that row 3 - raise the line rate - was abandoned. The threats section no longer states the link floor as a single number, since the bridge's packet granularity is now part of it and is specific to this bridge. Nine pages. Every figure still reads the raw per-trial CSVs, including the two new ones.
Diffstat (limited to 'examples/rf.zig')
0 files changed, 0 insertions, 0 deletions