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).
37 lines
1.8 KiB
Plaintext
37 lines
1.8 KiB
Plaintext
TURN RECORD: EXPORT-SIDE STATE AFTER THE IMPORT MILESTONE.
|
|
|
|
CONFIRMED AGAIN (client-driven, no pokes):
|
|
InitSession -> CreatePhoto(w6=1) -> SetTransport(mode=3, org=1)
|
|
-> PutTile => element+0x28 buffer holds 0xFF (white) / 0x00 (black)
|
|
Export(21) => err2 (BadValue); renderer runs with src_base = 00915FD0
|
|
(non-zero, verified at RP 0x1B296)
|
|
framebuffer => white and black captures byte-identical (AE = 0)
|
|
|
|
WHERE THE err2 COMES FROM -- narrowed this turn
|
|
slot21 between the extent check and the render call:
|
|
0x62F7E CALLA 0x7EA3432 ; drawable resource init/lookup
|
|
0x62F88 A5 = A8 ; JREQ 0x62FBC ; zero => continue, non-zero => return A5
|
|
and the callee (file 0x63432) returns:
|
|
0x634B0 MOVK 0x9 (BadDrawable) if *A11(0x160) == 0
|
|
So a failed drawable init would give err9, NOT err2. The err2 must therefore
|
|
come from a later path (0x62FDC CALLA 0x7EA47B6, or the render driver itself
|
|
returning 2 after 0x1B296).
|
|
Also checked: the target window's geometry is depth=1, 80x64 -- it MATCHES the
|
|
1-bit image, so depth mismatch is ruled out.
|
|
Creating the GC explicitly with function=GXcopy and plane-mask=1 changes
|
|
nothing (still err2, still no paint, AE=0).
|
|
|
|
STATUS. NO client-chosen image displayed. The window never changes.
|
|
|
|
WHAT IS SOLID
|
|
* The XIE import path is fully client-driven and verified inside the server
|
|
(element+0x28 -> 0xFF for white, 0x00 for black).
|
|
* src_base at rp+0x610 is non-zero (00915FD0 / 002909B0) with org=1.
|
|
* The export request passes every check the handler performs.
|
|
* The window is depth 1 and provably drawable (core-X PutImage control).
|
|
|
|
WHAT IS STILL UNKNOWN
|
|
The single remaining failure is inside the export/render completion path: the
|
|
renderer has a correct, populated source and still the client receives
|
|
BadValue, and the composited result never reaches the window.
|