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).
97 lines
2.7 KiB
Plaintext
97 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 XieQueryOpDefaults 3X "" "" "" "Digital" ""
|
|
...\" MANDOC->Begin OVERVIEW
|
|
.SH NAME
|
|
XieQueryOpDefaults \- This routine obtains the current operational default constraint
|
|
model from the server.
|
|
...\" MANDOC->End OVERVIEW
|
|
...\" MANDOC->Begin FORMAT
|
|
.SH C Format
|
|
\fI\fPXieQueryOpDefaults\fI(dpy, model_ret, levels_ret)\fP
|
|
...\" MANDOC->End FORMAT
|
|
...\" MANDOC->Begin TEMPLATE_PARA
|
|
.SH C Argument Information
|
|
...\" MANDOC->Begin CODE_EXAMPLE
|
|
.oS
|
|
Display *dpy;
|
|
int *model_ret;
|
|
unsigned long levels_ret[];
|
|
.oE
|
|
...\" MANDOC->End CODE_EXAMPLE
|
|
...\" MANDOC->End TEMPLATE_PARA
|
|
...\" MANDOC->VMS-specific, only valid keyword: HEADONLY
|
|
.SH RETURN VALUES
|
|
...\" MANDOC->Begin RETTEXT
|
|
None.
|
|
...\" 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 "model_ret" 20
|
|
The \fImodel_ret\fP argument specifies the pointer to
|
|
the location to which the routine returns the current constraint model
|
|
information.
|
|
...\" MANDOC->Begin TABLE
|
|
.PP
|
|
.TS
|
|
tab(@);
|
|
lfR lw(4.0i)fR .
|
|
.sp 4p
|
|
Symbol@Operation Performed
|
|
.sp 6p
|
|
XieK_HardClip@T{
|
|
Apply hard clip model
|
|
T}
|
|
.sp
|
|
XieK_ClipScale@T{
|
|
Apply clip scale model
|
|
T}
|
|
.sp
|
|
XieK_HardScale@T{
|
|
Apply hard scale model
|
|
T}
|
|
.sp
|
|
.TE
|
|
.PP
|
|
...\" MANDOC->End TABLE
|
|
.IP "levels_ret" 20
|
|
The \fIlevels_ret\fP argument specifies the
|
|
address of the array to which the routine returns the number of levels
|
|
to which each component is constrained. The length must be at least
|
|
equal to
|
|
XieK_MaxComponents.
|
|
...\" MANDOC->End PARAMDEFLIST
|
|
...\" MANDOC->Begin DESCRIPTION
|
|
.SH DESCRIPTION
|
|
This routine obtains the current operational default constraint
|
|
model from the server.
|
|
...\" MANDOC->End DESCRIPTION
|
|
...\" MANDOC->Begin TEMPLATE_PARA
|
|
.SH XIE Events and Error Messages
|
|
.PP
|
|
\fBProtocol Messages:\fP X_ieQueryOpDefaults
|
|
.PP
|
|
\fBXIE event returned:\fP None
|
|
.PP
|
|
\fBXieLib errors:\fP Reply error, BadLength
|
|
.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.
|