forked from opencode.energia.arti.ee/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).
41 lines
1.9 KiB
Plaintext
41 lines
1.9 KiB
Plaintext
TURN RECORD: err2 IS THE RENDER DRIVER'S RETURN CODE. EVERY EXPORT-SIDE STEP
|
|
SUCCEEDS.
|
|
|
|
Instrumented the whole export tail (slot 21, file 0x62D40) during a working
|
|
client-driven sequence:
|
|
|
|
ALLOC ret=00321C50 ; 0x6301C..0x6302A allocate the export context: OK
|
|
SETUP_before_render ; 0x63072 fills it (type 5, photo_id at +0x48,
|
|
; geometry at +0x88/+0xa8)
|
|
CALL_RD ; 0x63098 CALLA 0x07E5B152 == render driver 0x1B152
|
|
AFTER_RD a8=00000002 ; <-- the RENDER DRIVER RETURNS 2 (BadValue)
|
|
EPI a8=00000002 ; handler returns that value unchanged
|
|
|
|
Also confirmed on the same run:
|
|
* the drawable lookup at 0x62F7E (0x7EA3432) SUCCEEDS, so the handler jumps to
|
|
0x62FBC;
|
|
* at 0x62FBC the frame word is zero, so the second lookup (0x62FDC, the one I
|
|
was told to instrument) is SKIPPED -- it is never called on this path;
|
|
* the extent check at 0x62F12 passes;
|
|
* no BadValue site in the handler fires (EX_BADVALUE_1/2/3 never reached).
|
|
|
|
So the client's err2 is produced INSIDE 0x1B152, after that function has already:
|
|
* allocated rp (@0xa6000),
|
|
* stored src_base = *(element+0x28) = 00915FD0 at 0x1B238 (RP 0x1B296 fires
|
|
with src_base610 = 00915FD0),
|
|
* and with the element buffer verified to contain 0xFF for a white tile and
|
|
0x00 for a black tile.
|
|
|
|
MEANING: the export request, the drawable, the GC, the depth (window is depth 1),
|
|
the geometry, the extents and the source buffer are all correct. The single
|
|
remaining failure is inside the render driver's own processing of a valid,
|
|
populated source.
|
|
|
|
STATUS. NO client-chosen XIE image. The 64x64 window is unchanged; white and
|
|
black captures are byte-identical (AE = 0).
|
|
|
|
WHAT WOULD FINISH IT
|
|
The next instrumented range is 0x1B296.. the end of 0x1B152 (the render driver
|
|
is ~0x500 bytes of dense code and calls five helper routines). That is the
|
|
only place left where the BadValue can be produced.
|