Files
vt1200/xie/docs/dec/xie23/man/XieQueryMap.3X
T
arti d8d54bb990 feat(xie): a client-chosen XIE image is displayed on the VT1200
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).
2026-11-01 23:22:25 +02:00

110 lines
4.4 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 XieQueryMap 3X "" "" "" "Digital" ""
...\" MANDOC->Begin OVERVIEW
.SH NAME
XieQueryMap \- This routine returns the attributes of a server image.
...\" MANDOC->End OVERVIEW
...\" MANDOC->Begin FORMAT
.SH C Format
\fBXieQueryMap\fP\fI (pho_id, width_ret, height_ret, cmp_map_ret, cmp_cnt_ret,
cmp_lvl_ret, pxl_pol_ret, pxl_ratio_ret, pxl_prog_ret, scn_prog_ret,
constrained_ret)\fB
...\" MANDOC->End FORMAT
...\" MANDOC->Begin TEMPLATE_PARA
.SH C Argument Information
...\" MANDOC->Begin CODE_EXAMPLE
.oS
XiePhoto pho_id;
unsigned long *width_ret;
unsigned long *height_ret;
unsigned char *cmp_map_ret;
unsigned char *cmp_cnt_ret;
unsigned char *cmp_lvl_ret;
unsigned char *pxl_pol_ret;
double *pxl_ratio_ret;
unsigned char *pxl_prog_ret;
unsigned char *scn_prog_ret;
unsigned char *constrained_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 "pho_id" 20
The \fIpho_id\fP argument specifies the identifier of the image you want to
query. The image can be an unbound photomap, a photomap bound to a photoflo,
a phototap, or a photoflo. The photoflo is specified explicitly if
the image is a photoflo, or implicitly if the image is a photomap bound
to the photoflo or a phototap. If the image is a photoflo, the routine
queries the photomap or phototap currently at the end of the photoflo.
.IP "width_ret" 20
The \fIwidth_ret\fP argument specifies the pointer to
the location to which the routine returns the width attribute.
.IP "height_ret" 20
The \fIheight_ret\fP argument specifies the pointer to
the location to which the routine returns the height attribute.
.IP "cmp_map_ret" 20
The \fIcmp_map_ret\fP argument specifies the pointer to
the location to which the routine returns the component mapping attribute.
.IP "cmp_cnt_ret" 20
The \fIcmp_cnt_ret\fP argument specifies the pointer to
the location to which the routine returns the component count attribute.
.IP "cmp_lvl_ret" 20
The \fIcmp_lvl_ret\fP argument specifies the pointer to
the array to which the routine returns the bits per
component attribute. The array length must be at least equal to
XieK_MaxComponents.
.IP "pxl_pol_ret" 20
The \fIpxl_pol_ret\fP argument specifies the pointer to
the location to which the routine returns the pixel polarity attribute.
.IP "pxl_ratio_ret" 20
The \fIpxl_ratio_ret\fP argument specifies the pointer to
the location to which the routine returns the pixel aspect ratio attribute.
.IP "pxl_prog_ret" 20
The \fIpxl_prog_ret\fP argument specifies the pointer to
the location to which the routine returns the pixel progression attribute.
.IP "scn_prog_ret" 20
The \fIscn_prog_ret\fP argument specifies the pointer to
the location to which the routine returns the scanline progression attribute.
.IP "constrained_ret" 20
The \fIconstrained_ret\fP argument specifies the pointer
to the location where the routine returns the Boolean flag indicating
whether or not the image data is constrained.
...\" MANDOC->End PARAMDEFLIST
...\" MANDOC->Begin DESCRIPTION
.SH DESCRIPTION
This routine returns the attributes of a server image. If you do not
want to retrieve a particular attribute, set the associated pointer to null.
...\" MANDOC->End DESCRIPTION
...\" MANDOC->Begin TEMPLATE_PARA
.SH XIE Events and Error Messages
.PP
\fBProtocol Messages:\fP X_ieQueryResource
.PP
\fBXIE event returned:\fP None
.PP
\fBXieLib errors:\fP Reply error, BadLength
.PP
Returns null if invalid photomap
.PP
\fBXieServer errors:\fP BadIDChoice -- Invalid identifier
...\" MANDOC->End TEMPLATE_PARA
...\"
...\" This source file has been processed by the osf_build_manpages
...\" script. Contact dlibrary@ravine if you need more information.