mirror of
https://git.k-space.ee/arti/vt1200.git
synced 2026-11-03 12:33:16 +02:00
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).
19 lines
1.1 KiB
Lua
19 lines
1.1 KiB
Lua
-- bisect file 0x6BA1E..0x6BAC4 on the arm path (10 breakpoints)
|
|
local frames = 0
|
|
local dbg = manager.machine.debugger
|
|
dbg:command("bpset 0x3F53D820,,{ printf \"A_REGIDSTORE id=%08X obj=%08X\n\", d@(a9+0x40), a11 ; g }")
|
|
dbg:command("bpset 0x3F55D0F0,,{ printf \"B_6BA1E cls2entry arg1=%08X\n\", d@(a13+0xffc0) ; g }")
|
|
dbg:command("bpset 0x3F55D120,,{ printf \"C_6BA24 copy_byte40_out\n\" ; g }")
|
|
dbg:command("bpset 0x3F55D190,,{ printf \"D_6BA32 byte40_zero_check\n\" ; g }")
|
|
dbg:command("bpset 0x3F55D1F0,,{ printf \"E_6BA3E err_0E_byte40\n\" ; g }")
|
|
dbg:command("bpset 0x3F55D330,,{ printf \"F_6BA66 err_0E_other\n\" ; g }")
|
|
dbg:command("bpset 0x3F55D510,,{ printf \"G_6BAA2 merge\n\" ; g }")
|
|
dbg:command("bpset 0x3F55D560,,{ printf \"H_6BAAC store_5a8\n\" ; g }")
|
|
dbg:command("bpset 0x3F55D5C0,,{ printf \"I_6BAB8 outcell_test a7=%08X\n\", d@(a13+0xff20) ; g }")
|
|
dbg:command("bpset 0x3F55D620,,{ printf \"J_6BAC4 err_0A\n\" ; g }")
|
|
print("XIE-MIN4 armed 10 breakpoints")
|
|
emu.register_frame_done(function()
|
|
frames = frames + 1
|
|
if frames >= 2000000 then machine:exit() end
|
|
end, "min4")
|