forked from arti/vt1200
arti
d8d54bb990
The XIE path now runs end to end: XieCreateImage -> XieCreatePhoto ->
XiePutTile -> XieExport(photomap -> depth-1 pixmap) -> XCopyArea(pixmap ->
window), and the client's tile appears on screen at the client's own window
position, pixel-exact.
TWO FAULTS BEHIND THE LONG DEAD END
1. Device model (harness/mame/vt1200.cpp, opt-in VT1200_ACCEL=1). The
accelerator's output port 0x5600200 returns the pixel stream the firmware
pushed into the FIFO -- the firmware then stores it into the drawable itself
(file 0x125528: MOVE *B6,*B1 ; ADDK 0x10,B1). The FIFO read pointer was
never reset between transfers, so consecutive exports read stale words and
the same fill produced 759 then 516 set pixels. Reset m_fifo_in/out on the
data-register write; the export is now deterministic.
2. Measurement, not the device.
- dwt/screenshot.py without --real reads 1024x1024 at a 128-byte row stride,
but the VR319 default programs 1280x1024 at a 2048-bit (256-byte) pitch.
That is the "shifted" picture; --real is the correct read.
- The earlier "0 differing bytes over 128 KiB" VRAM comparison stepped peek
by 1024 *bit* addresses, so it scanned rows 0..63 only -- never the window
at rows 200..263. Over the real raster the white/black diff is 576 bytes
spanning exactly those rows.
- New instrument: decclient does a server-side XGetImage readback of the
pixmap and window and counts set pixels. That separated "the server never
drew it" from "the framebuffer view is wrong".
EVIDENCE (reproduced twice, the second time from a fresh machine)
no export vs 0xFF : 4096 / 4096 pixels differ
no export vs 0x00 : 0 / 4096 (the window background is black)
0xFF vs 0x00 : 4096 / 4096
0xAA vs 0x0F : 2048 / 4096 (the two stripe phases)
Tile byte 0xAA reproduces as 1-pixel vertical stripes, 0x0F as 4-pixel, with
no shear -- so the placement is right and the pixels are the client's.
Contents: xie/ holds DEC XIE 2.3 headers, 84 man pages and complete
client+server source; a libXie.a and decclient built from DEC's own code; the
XIE probes; and evidence/ with every measurement, including explicit
retractions of the earlier wrong readings (VRAM_IDENTICAL_FOR_BOTH_FILLS and
friends). xie/evidence/XIE_IMAGE_DISPLAYED.md is the report; frames are in
xie/evidence/png/.
The accelerator model stays opt-in: it answers the status poll and relays the
pixel stream, but performs no compositing, so it is a stand-in and the verified
default configuration is unchanged (a no-env run still parks in the level-0
diagnostics menu at PC=3FDCE400).
35 lines
1.6 KiB
Plaintext
35 lines
1.6 KiB
Plaintext
TURN RECORD: THE EXPORT HANDLER SIMPLY PROPAGATES THE RENDER DRIVER'S CODE.
|
|
(Undecoded code at 0x630BC..0x630E7 was the missing link; now read.)
|
|
|
|
0x630B6 CALLA 0x07F63B00 ; free the export context
|
|
0x630BC A5 = *A13(0x120) ; <-- the RENDER DRIVER's return value
|
|
0x630C0 JREQ 0x630E8 ; zero -> SUB A8,A8 -> return 0 (success)
|
|
0x630C2 ... error report ...
|
|
0x630E2 A8 = *A13(0x120)
|
|
0x630E6 JR 0x630EA ; return the render driver's code unchanged
|
|
|
|
So everything the export handler does -- lookup, three range checks, extent
|
|
computation, drawable init, context allocation, finalize -- either succeeds or is
|
|
not reached, and the value the client sees is precisely what 0x1B152 returned.
|
|
|
|
Combined with previous turns:
|
|
0x1B852 AFTER_FINALIZE a8 = 0 (finalizer succeeds)
|
|
0x39F5E BadValue site NOT firing (rp byte 4 already 1)
|
|
err2 therefore comes from elsewhere inside 0x1B152 after 0x1B852.
|
|
|
|
CLIENT-SIDE STATE (unchanged, reproducible):
|
|
CreatePhoto(w6=1) -> SetTransport(mode=3, component_organization=1) -> PutTile
|
|
element+0x28 buffer = 0xFF (white) / 0x00 (black)
|
|
QueryResource: comp_COUNT=1, 64x64, constrained
|
|
Export(minor 21):
|
|
src_base (rp+0x610) = 008FD510 / 00915FD0 (non-zero)
|
|
returns err2; window unchanged; white vs black captures differ only by the
|
|
Terminal Manager's own figures and the cursor (AE 1186-2950)
|
|
|
|
STATUS. NO client-chosen XIE image. xshow (core X) remains the only viewer that
|
|
has displayed an image.
|
|
|
|
REMAINING SCOPE: strictly inside one function (0x1B152, ~0x500 bytes) after
|
|
0x1B852, on a code path that has a valid source, a successful finalize, and still
|
|
produces 2.
|