forked from arti/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).
46 lines
2.4 KiB
Plaintext
46 lines
2.4 KiB
Plaintext
RAW SOCKET DUMP -- the reply parser is correct, but a CREATE CAN FAIL *AFTER*
|
|
it has already allocated and registered the object. That invalidates a large
|
|
class of earlier measurements.
|
|
|
|
Method: one connection, then send raw requests and hexdump whatever comes back
|
|
(no parsing assumptions).
|
|
|
|
create (minor 8, 12 words):
|
|
00 0e 03 00 | 02 10 47 00 | 08 00 81 00 | 20 00 00 00 | e0 56 41 00 ...
|
|
arm (minor 20, 35 words):
|
|
00 0e 04 00 | 02 10 47 00 | 14 00 81 00 | 00 00 00 00 | 20 00 00 00 ...
|
|
put (minor 19, 23 words):
|
|
00 0e 05 00 | 02 10 47 00 | 13 00 81 00 | 40 57 41 00 | 30 22 29 00 ...
|
|
|
|
Decoding as an X11 Error packet (type, error_code, sequence, bad_value,
|
|
minor_code, major_code):
|
|
create: type=0 code=0x0e (14 BadIDChoice) seq=3 bad=0x00471002 minor=0x0008 major=0x0081
|
|
arm : type=0 code=0x0e (14 BadIDChoice) seq=4 bad=0x00471002 minor=0x0014 major=0x0081
|
|
put : type=0 code=0x0e (14 BadIDChoice) seq=5 bad=0x00471002 minor=0x0013 major=0x0081
|
|
|
|
So the parser's error vocabulary is CORRECT (byte 1 is the error code; bytes 8-9
|
|
are the minor; byte 10 is 0x81 = the XIE extension opcode). That part of the
|
|
tooling is sound.
|
|
|
|
BUT: in this very same run the REGIDSTORE breakpoint (file 0x67B04, the ID-store
|
|
inside create) fired -- i.e. the server DID allocate an object and register it
|
|
under id 0x00471002 -- and the create request still returned BadIDChoice(14),
|
|
with bad_value = that same id.
|
|
|
|
That means create can fail LATE: the resource is allocated/registered first and a
|
|
subsequent validation rejects the request. Consequences for earlier work:
|
|
|
|
* Any sequence where "create = no-reply" was recorded (the reply was very often
|
|
not read back) must be treated as UNKNOWN, and may in fact have been this
|
|
late BadIDChoice.
|
|
* Measurements that attributed an error to arm or put may instead be reporting a
|
|
resource whose create had failed -- the arm/put then correctly answer
|
|
BadIDChoice because the id is not usable, even though an object exists.
|
|
* This is the most likely root of the ERR8 / ERR10 / ERR14 inconsistency across
|
|
runs that caused several retractions.
|
|
|
|
NEXT REQUIRED FIX before any further conclusions: read EVERY reply and assert it
|
|
is a success before proceeding (fail the step otherwise). The earlier
|
|
"create=no-reply" lines must be re-run with reply checking; only sequences whose
|
|
create, arm and put all report success are usable evidence.
|