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).
57 lines
2.9 KiB
Plaintext
57 lines
2.9 KiB
Plaintext
TURN RECORD: THE DISPLAY HALF STILL FAILS; TWO STRUCT FACTS CORRECTED.
|
|
|
|
A) QueryExport RETURNS PIXELS, NOT A PIXMAP
|
|
xieQueryExportReply (XieProto.h) = { type, _reserved, sequenceNumber, length,
|
|
pixel_count, lut_id, lut_mapping, _pad[15] }.
|
|
So minor 24 reports how many colormap pixels the export allocated (plus an
|
|
optional LUT id). There is NO pixmap id to XCopyArea -- "export paints
|
|
straight to the drawable". My earlier plan of copying a pixmap to the window
|
|
was based on a wrong assumption and is dropped.
|
|
|
|
B) XieExport.3X ERROR TABLE (read in full)
|
|
BadIDChoice Invalid identifier
|
|
BadAlloc Insufficient server resources
|
|
BadDrawable Invalid X11 drawable
|
|
BadGC Invalid graphics context
|
|
BadMatch source image is not constrained / gc not compatible with the
|
|
drawable / LUT has fewer levels than the source / LUT not
|
|
compatible with the drawable levels / source image not
|
|
compatible with the drawable
|
|
Note there is no BadValue in this list, yet a correctly-idded export returns
|
|
err2 (BadValue), so the failure is not one of the documented export
|
|
conditions.
|
|
|
|
C) THE BadDrawable WAS MY BUG
|
|
In the previous A/B run I hard-coded window/gc ids (0x55300/0x55400) instead
|
|
of using c.new_id(), so the drawable id was never valid. Re-run with real
|
|
ids:
|
|
white/black: transport=ok puttile=ok export=err2 src_base=00000000
|
|
trace RP/TYPE5
|
|
i.e. BadDrawable disappears; BadValue remains.
|
|
|
|
D) BOUND PATH WITH THE CORRECTED OPERAND ORDER
|
|
xieBindPhotomapReq = { photoflo_id, photomap_id }. Sequence
|
|
create photomap(w6=1) -> SetTransport(mode=3) -> PutTile(ok)
|
|
-> create photoflo(type=1, w6=1) (ok) -> BindPhotomap {flo,map} (ok)
|
|
-> Export -> ExecutePhotoflo(13)
|
|
gives: export = err1 (BadRequest) x6, execute = err1 x6, renderer trace
|
|
(none). So once bound, minor 21/13 are rejected outright -- the bound path is
|
|
not usable with the operand shapes I have.
|
|
|
|
E) WINDOW IS PROVABLY DRAWABLE
|
|
Control (unchanged): core-X PutImage into the same 64x64 window produces a
|
|
visible block in dwt/screenshot.py. So any successful XIE paint would be
|
|
visible; the absence of change is real.
|
|
White vs black captures continue to differ only by the Terminal Manager's own
|
|
figures and the cursor (2697-2950 px).
|
|
|
|
STATUS. Still NO client-chosen XIE image. src_base (rp+0x610) 00000000 in every
|
|
run; the window is unchanged by XIE; xshow (core X) remains the only viewer that
|
|
has displayed an image.
|
|
|
|
WHERE IT STANDS: the import half is complete and verified by the server's own
|
|
QueryResource (comp_COUNT=1, 64x64, constrained). The display half has exactly
|
|
two observable failure modes left -- unbound photomap => renderer entered but
|
|
src_base 0, bound photomap => BadRequest on export/execute -- and the documented
|
|
error conditions in XieExport.3X do not cover either.
|