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).
28 lines
1.5 KiB
Plaintext
28 lines
1.5 KiB
Plaintext
THE armF STATE, TRACED. Three distinct lookup codes, one per arming choice.
|
|
|
|
One connection: I = create op=2 (image), F = create op=1 (photoflo).
|
|
|
|
create I 0x40C000 -> OK REGIDSTORE id=0040C000 obj=003FDC50 ; REGISTER
|
|
create F 0x40D000 -> OK REGIDSTORE id=0040D000 obj=00388090 ; REGISTER
|
|
|
|
arm F (v16=1) then PUT_TILE I -> S19LOOK a8=0000000A (BadAccess, 10)
|
|
arm I (v16=1) then PUT_TILE I -> S19LOOK a8=00000008 (BadMatch, 8)
|
|
PUT_TILE F (never armed) -> S19LOOK a8=0000000E (BadIDChoice, 14)
|
|
|
|
So arming the photoflo genuinely changes WHICH failure the typed lookup reports:
|
|
it gets past the stage that produces BadMatch and stops at a BadAccess check.
|
|
That is a real state difference, not noise, and it is the only one found.
|
|
|
|
Caveat on the LOOK breakpoint (0x6BA38): it prints cls=01 in both the armF and
|
|
armI cases, and earlier it printed an incrementing 01,02,03 across successive
|
|
calls. That means A7 at 0x6BA38 is NOT the resource struct -- it is the export
|
|
element (the same buffer whose +0x28 is src_base). So LOOK's "cls" and "b40"
|
|
columns are not resource fields and must not be read as such; only S19LOOK's
|
|
return code (a8 at 0x6A7B4) is trustworthy in that trace.
|
|
|
|
Registration sites during armF/put: 0 hits (they fire only inside create).
|
|
|
|
CONCLUSION: arming the photoflo advances the import lookup past BadMatch to
|
|
BadAccess. That is the furthest any configuration has reached. No configuration
|
|
reached the handoff (0x6B640) or wrote src_base.
|