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).
76 lines
2.7 KiB
Plaintext
76 lines
2.7 KiB
Plaintext
...\" This manpage source uses rsml coding.
|
|
.so /usr/share/lib/tmac/sml
|
|
.so /usr/share/lib/tmac/rsml
|
|
...\"
|
|
...\" *********************************************************************
|
|
...\" * *
|
|
...\" * Copyright (c) Digital Equipment Corporation, 1992 *
|
|
...\" * *
|
|
...\" * All Rights Reserved. *
|
|
...\" * *
|
|
...\" *********************************************************************
|
|
.TH XieCheckFunction 3X "" "" "" "Digital" ""
|
|
...\" MANDOC->Begin OVERVIEW
|
|
.SH NAME
|
|
XieCheckFunction \- This routine checks for the availability of server support for a
|
|
specified XIE protocol function.
|
|
...\" MANDOC->End OVERVIEW
|
|
...\" MANDOC->Begin FORMAT
|
|
.SH C Format
|
|
\fIstring\fP = XieCheckFunction\fI(dpy, function)\fP
|
|
...\" MANDOC->End FORMAT
|
|
...\" MANDOC->Begin TEMPLATE_PARA
|
|
.SH C Argument Information
|
|
...\" MANDOC->Begin CODE_EXAMPLE
|
|
.oS
|
|
char *string;
|
|
Display *dpy;
|
|
int function;
|
|
.oE
|
|
...\" MANDOC->End CODE_EXAMPLE
|
|
...\" MANDOC->End TEMPLATE_PARA
|
|
...\" MANDOC->VMS-specific, only valid keyword: HEADONLY
|
|
.SH RETURN VALUES
|
|
...\" MANDOC->Begin RETTEXT
|
|
The routine returns a pointer to a character string that describes the
|
|
protocol function in the \fIstring\fP argument.
|
|
If the server does not support the function,
|
|
the routine returns a null value. The \fIstring\fP argument
|
|
should not be freed.
|
|
...\" MANDOC->End RETTEXT
|
|
...\" MANDOC->Begin PARAMDEFLIST
|
|
.SH PARAMETERS
|
|
.IP "dpy" 20
|
|
The \fIdpy\fP argument specifies the
|
|
X11 display identifier returned by the XOpenDisplay routine.
|
|
.IP "function" 20
|
|
The \fIfunction\fP argument specifies the XIE protocol
|
|
function minor op-code that you want to check. The valid range is from
|
|
0 to 255. For a list of minor op-code symbols, refer to the applicable
|
|
include file.
|
|
...\" MANDOC->End PARAMDEFLIST
|
|
...\" MANDOC->Begin DESCRIPTION
|
|
.SH DESCRIPTION
|
|
This routine checks for the availability of server support for a
|
|
specified XIE protocol function.
|
|
This routine returns a pointer to a character string that describes
|
|
whether or not your server supports the specified XIE protocol function.
|
|
If the server does not support the function, the routine returns a null
|
|
pointer.
|
|
...\" MANDOC->End DESCRIPTION
|
|
...\" MANDOC->Begin TEMPLATE_PARA
|
|
.SH XIE Events and Error Messages
|
|
.PP
|
|
\fBProtocol Messages:\fP None
|
|
.PP
|
|
\fBXIE event returned:\fP None
|
|
.PP
|
|
\fBXieLib errors:\fP None
|
|
.PP
|
|
\fBXieServer errors:\fP None
|
|
...\" MANDOC->End TEMPLATE_PARA
|
|
|
|
...\"
|
|
...\" This source file has been processed by the osf_build_manpages
|
|
...\" script. Contact dlibrary@ravine if you need more information.
|