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).
45 lines
2.4 KiB
Plaintext
45 lines
2.4 KiB
Plaintext
DOCUMENTED DISPLAY PATH IMPLEMENTED: export -> QUERY_EXPORT -> XCopyArea -> GetImage.
|
|
|
|
Source of the model: docs/EK-V120I-IN-001_installing-DECimage-1200.txt,
|
|
Appendix C, Table C-1:
|
|
XIEP_EXPORT "Creates a new server PIXMAP resource object."
|
|
XIEP_QUERY_EXPORT "Queries the export context."
|
|
and: "When displaying an image by copying from a pixmap ... using XCopyArea
|
|
or XCopyPlane ..."
|
|
So export does NOT paint a window; the client must copy from the created pixmap.
|
|
|
|
IMPLEMENTED AND MEASURED (valid c.new_id ids, no-reply model, one connection;
|
|
core-X requests sent on the same socket so the pixmap is in the right client):
|
|
|
|
EXPORT (slot 21) -> no reply (success)
|
|
QUERY_EXPORT (minor 10, op 3) -> REPLY with 4 words + 4 extra:
|
|
head : 0x40, 0x40, <ptr>, 0x80000000, 0x01000000, <id-like>
|
|
extra: 2, 0, <ptr>, <resource id>
|
|
op 3 and op 4 reply; ops 1,2,5,6 -> BadIDChoice. w/h = 64,64 correct.
|
|
XCopyArea(pixmap_candidate -> window, gc) -> BadDrawable every time
|
|
GetImage(window) -> unchanged
|
|
|
|
The "<id-like>" field VARIES every run: 0x00920101, 0x00380101, 0x00330101,
|
|
0x00360101 across four runs. Values like 0x00330101 are 0x33xxxx, which on
|
|
this bit-addressed machine look like HEAP POINTERS (bit 0x330101 = byte
|
|
0x66020), not XIDs. XCopyArea rejects each with BadDrawable.
|
|
|
|
Result, both tile contents:
|
|
solid-white tile: window nz 512 -> 512, changed=False
|
|
solid-black tile: window nz 512 -> 512, changed=False
|
|
white vs black identical: True
|
|
first bytes both: 88888888888888882222222222222222 (the window stipple)
|
|
|
|
CONCLUSION: the documented model is confirmed in principle -- export creates a
|
|
server pixmap and the client is expected to copy it -- but the export context
|
|
reply does not expose a usable pixmap XID (it carries 64x64, server pointers and
|
|
the resource id). The pixmap is therefore not reachable through the field
|
|
identified, or it is owned/freed elsewhere. The window still never changes.
|
|
|
|
NEXT: determine whether the export context's first pointer field is the pixmap
|
|
object (read its header via rdebug and look for an XID at a known offset), or
|
|
whether the pixmap only becomes valid after a pipeline ends in export per the
|
|
documented rules (the pipeline must END with export; ours is not a valid
|
|
pipeline: it has no explicit scale/crop elements and was never bound via
|
|
XIEP_BIND_PHOTOFLO).
|