ACCELERATOR REGISTER MAP, WITH THE FIRMWARE PC THAT WRITES EACH ONE.

Captured during a COMPLETING export (VT1200_ACCEL=1 + compression poke):
  writes 180, reads 591.  Reads: 0x5600200 x384, 0x5600100 x102, 0x5600010 x100,
  0x5600030 x5.

  address    count  sample values                       writer PC -> file
  0x5600000    2    0000                                3F3B6A40 -> 0x36D48
  0x5600020    3    0248 / 0248 / 0258                  3F3B6090 -> 0x36C12
                                                        3F3B6A00 -> 0x36D40
                                                        3FB16EF0 -> 0x125DDE
  0x5600030    8    0032 0033 0432 0232 0233 0032       multiple
  0x5600040    1    0040                                3F3B6D30 -> 0x36DA6
  0x5600050    1    0000                                (flush)
  0x5600080  154    parameter table (idx/value pairs)    0x1B44C..
  0x5600100   11    0000 0001 0002 0008 0200 0202 0201  multiple
  0x5600200  (read 384x)                                <-- output/status FIFO

WHAT 0x5600040 IS
  file 0x36DA0:   MOVE A11,@0x5600040,0x0
  where A11 = *A13(0x240), a frame scalar.  Observed value 0x40 = 64, i.e. a
  dimension (strip height or pitch).  The same block then calls 0x7F6538C with
  six frame arguments -- the transfer setup.

INTERPRETATION
  * 0x5600030 is a control register whose value toggles bit 9 (0x200) and bit 10
    (0x400):  0032 -> 0432 -> 0232 -> 0032, and 0201/0202 on 0x5600100.
  * 0x5600100 is the command register (0x200 / 0x201 / 0x202 / 0x0008 ...).
  * 0x5600200 is read 384x -- almost certainly the engine's output/data port.
  * the parameter table at 0x5600080 carries coefficients, not pixels.

  So the engine is programmed with (dimension, coefficients, command) and is then
  expected to move pixels itself.  No CPU-visible source/destination pointer is
  written: 16-bit writes only, and no value in the 0x10..0x1ffffff (main RAM) or
  >=0x04000000 (VRAM) ranges appears anywhere in the write stream.

STATE
  * export completes, no error;
  * framebuffer unchanged; NO client-chosen XIE image displayed;
  * model opt-in (VT1200_ACCEL=1); default configuration intact;
  * xshow (core X) is still the only viewer that has shown an image.
