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).
39 lines
1.8 KiB
Plaintext
39 lines
1.8 KiB
Plaintext
TURN RECORD: SCAN OF THE RENDER DRIVER AFTER 0x1B296.
|
|
|
|
Static scan of 0x1B296..0x1B6E0 for everything that could yield the A8=2 the
|
|
export handler returns:
|
|
|
|
0x1B360 MOVK 0x2,A11 ; 0x1B362 MOVB *A11,*A5(0x58)
|
|
-- this is the ELEMENT-TYPE store (type 2), NOT an error. It writes
|
|
the element type into the render-params block; I had earlier
|
|
chased this as a possible BadValue and it is not one.
|
|
|
|
0x1B3C4..0x1B43E the render worker's helper calls
|
|
CALLA 0x07FC229C (x5), 0x07FC1EB2 (x2), 0x07FC1F5E (x2), 0x07FC2210 (x2)
|
|
-- the actual per-element processing; these return codes are the
|
|
remaining candidates for A8=2.
|
|
|
|
0x1B5FA..0x1B67A drawable-bind path: returns MOVK 0x18 and then MOVK 0x9
|
|
(BadDrawable), NOT 2.
|
|
0x1B68C..0x1B6E2 gc-bind path: returns MOVK 0xd (BadGC), NOT 2.
|
|
0x1B612 / 0x1B6A0 CALLA 0x07F174A4 (bind helper)
|
|
0x1B672 CALLA 0x07EFFA5E (send-error helper)
|
|
|
|
So there is NO `MOVK 0x2` that sets A8 anywhere in the scanned range: the A8=2
|
|
observed at AFTER_RD (0x6309E) is a value RETURNED by one of the 0x7FC2xxx
|
|
helpers and propagated out of the driver unchanged.
|
|
|
|
MEASURED (unchanged, reproducible):
|
|
import: element+0x28 -> 0xFF (white) / 0x00 (black), QueryResource comp_COUNT=1
|
|
export: all handler checks pass, context alloc OK (ret=00321C50),
|
|
render driver called at 0x63098, returns a8=2, handler returns it
|
|
window: 64x64, depth 1, provably drawable (core-X PutImage control)
|
|
framebuffer: white vs black byte-identical (AE = 0)
|
|
|
|
STATUS. NO client-chosen XIE image. xshow (core X) remains the only viewer
|
|
that has displayed an image.
|
|
|
|
WHERE IT IS NOW: the last unidentified return is inside the 0x7FC2xxx helper
|
|
family invoked between 0x1B3C4 and 0x1B43E. That is the only place left that
|
|
can produce the 2.
|