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).
40 lines
1.7 KiB
Plaintext
40 lines
1.7 KiB
Plaintext
TURN RECORD: FIRMWARE CONVERSION HELPERS PROBED DURING A REAL EXPORT.
|
|
|
|
Addresses derived from the CALLA immediates (file = cal - 0x7E40000):
|
|
0x07FC229C -> file 0x18229C (bit 0x3FE114E0)
|
|
0x07FC1EB2 -> file 0x181EB2 (bit 0x3FE0F590)
|
|
0x07FC1F5E -> file 0x181F5E (bit 0x3FE0FAF0)
|
|
0x07FC2210 -> file 0x182210 (bit 0x3FE11080)
|
|
|
|
Run: ./xie/build/dec/decclient 192.168.99.2:0 ff 3 (the genuine 2.3 client,
|
|
org=BandByPlane, export straight to the window)
|
|
|
|
MEASURED:
|
|
image: org=3 w=64 h=64 levels=2,0,0 arSize=4096
|
|
photomap created
|
|
put tile sent
|
|
X Error: BadValue, Major 129 (Xie), Minor 21 (Export)
|
|
|
|
trace:
|
|
H1EB2 a0=003F09B0 a1=00000000 a8=40C4D134
|
|
H1EB2 a0=003F09B0 a1=00000000 a8=44CFF000
|
|
|
|
H229C (0x7FC229C) never fired, H1F5E and H2210 never fired, and none of the
|
|
post-call sites (R_C4 / R_E2 / R_10 / R_44) fired either.
|
|
|
|
So with org=BandByPlane the export does NOT go through the per-element block at
|
|
0x1B3C4..0x1B43E at all -- the only conversion helper reached is 0x7FC1EB2, twice,
|
|
with the same source pointer (0x3F09B0) and a1 = 0, and float-looking results in
|
|
A8 (0x40C4D134 / 0x44CFF000). Those are the only two conversion calls observed.
|
|
|
|
INTERPRETATION (not yet proven): 0x7FC1EB2 is being used as a numeric helper
|
|
(its outputs look like IEEE singles), not as the pixel mover; the pixel-moving
|
|
call that would fail is not reached, which is consistent with BadValue being
|
|
raised before any real conversion.
|
|
|
|
STATE (unchanged): no client-chosen image displayed; window untouched; white vs
|
|
black captures differ only by Terminal Manager figures and cursor.
|
|
xshow (core X) remains the only viewer that has shown an image.
|
|
|
|
STATUS. NO client-chosen XIE image.
|