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).
55 lines
2.9 KiB
Plaintext
55 lines
2.9 KiB
Plaintext
MAJOR: DEC XIE 2.3 CLIENT **AND SERVER** SOURCE OBTAINED; THE CREATE REQUEST IS
|
|
NOW DECODED EXACTLY AND levels IS FIXED (was 1, now 2).
|
|
|
|
A) SOURCE (peer session, from OSF/1 2.0 source kits; copied to xie/docs/dec/xie23-src/)
|
|
include/ XieProto.h (XieK_MajorVersion 2 / MinorVersion 3) etc.
|
|
lib/xie/ XIElib client library, 9,723 lines (9 C files)
|
|
server/xie/ 107 files -- the server: XieDisplay.c, XieTransport.c,
|
|
XieResource.c, and smi/ (SmiConvert.c SmiCrop.c SmiScale.c
|
|
SmiRotate.c SmiPipe.c ...), plus decimage-ids/ glue.
|
|
This is the actual implementation of the code I have been disassembling.
|
|
|
|
B) THE CREATE REQUEST IS `xieCreatePhotoReq` (48 bytes = 12 words):
|
|
+4 resource_type +8 resource_id +12 width +16 height
|
|
+20 aspect_ratio (XieFloatRec, 8 bytes)
|
|
+28 levels[XieK_MaxComponents=3] (12 bytes)
|
|
+40 number_of_components +41 component_mapping
|
|
+42 pixel_progression +43 line_progression
|
|
+44 polarity +45 pad[3]
|
|
So in 32-bit data words:
|
|
w0 type, w1 id, w2 width, w3 height, w4/w5 aspect, w6 levels[0],
|
|
w7 levels[1], w8 levels[2],
|
|
w9 = noc | map<<8 | pxprog<<16 | lnprog<<24, w10 = polarity
|
|
MY OLD PAYLOAD SET w6=1 (levels[0]=1 => 0 bits/pixel) and w9=0x100
|
|
(number_of_components = 0). Corrected to:
|
|
levels = (2,2,2), noc=1, component_mapping=XieK_Bitonal(1),
|
|
pxprog=XieK_BandByPixel(1), lnprog=XieK_BandByLine(2), polarity=1
|
|
VERIFIED: QueryResource now reports levels=(2, ...) and comp_COUNT=1
|
|
(it was levels=(1, ...) before).
|
|
|
|
C) SERVER EXPORT PATH (XieDisplay.c) -- now read from source, not inferred
|
|
ProcExport: LookupPhotos_ -> MatchOkIf_(Constrained_(img))
|
|
x=max(src_x,0); y=max(src_y,0);
|
|
w=min(src_x,0)+width; h=min(src_y,0)+height;
|
|
w = Width_(img) < x+w ? Width_(img) -x : w;
|
|
h = Height_(img) < y+h ? Height_(img)-y : h;
|
|
ValueOkIf_( w > 0 && h > 0 ) <- the only BadValue here
|
|
CreateExportContext(...) ; Format(...) ; Export(...)
|
|
CreateExportContext contains NO ValueOkIf_ at all, and XieDisplay.c contains
|
|
no BadValue literal -- so a BadValue must come from a callee
|
|
(CvtZPixmap -> DdxConvert_ -> SmiConvert).
|
|
Checked: SmiConvert's unsupported path returns **BadImplementation (17)**, not
|
|
BadValue(2). So that is not the source either.
|
|
|
|
D) STILL OPEN: what returns 2. The candidates are now a small set inside the
|
|
conversion/export callees, and the source makes this readable rather than
|
|
guessable.
|
|
|
|
STATE
|
|
import verified (element+0x28 = 0xFF white / 0x00 black)
|
|
create now correct (levels=2, noc=1)
|
|
export still err2 ; window never changes ; white vs black AE = 2040 (stats+cursor)
|
|
xshow (core X) remains the only viewer that has displayed an image
|
|
|
|
STATUS. NO client-chosen XIE image.
|