okay. so the logical conclusion of all that is...
since we can start the Xserver AND point x11vnc at it AND run xvncviewer.
[root@kindle root]#
/mnt/us/Xfbdev -fp /mnt/us/sh/fonts/X11/100dpi/ -noreset -nolisten tcp -screen 600x800x8 -bs -wr
IF xvncviewer could point to x11vnc started in a shared mode like:
[root@kindle lib]#
x11vnc -noxdamage -noncache -shared -forever
[root@kindle root]#
/mnt/us/kindlevncviewer/kvncviewer.sh kindle:0
and then on the PC: you could just "step in" to add control. like:
vnc <kindle ip or hostname>
where vnc was:
Quote:
#!/bin/bash
xtightvncviewer -encodings "tight copyrect" -depth 4 -compresslevel 1 $@ &
sleep 2;
# make it tidy
wmctrl -x -r Tight -e 0,0,0,600,800
wmctrl -x -r Tight -b toggle,fullscreen
|
sadly this does not work as there appears to be some ZRLE (or perhaps just "expected" formatting) errors when trying this:
[root@kindle root]#
/mnt/us/kindlevncviewer/kvncviewer.sh kindle:0
Quote:
01/11/2012 15:57:32 VNC server supports protocol version 3.8 (viewer 3.8)
01/11/2012 15:57:32 We have 1 security types to read
01/11/2012 15:57:32 0) Received security type 1
01/11/2012 15:57:32 Selecting security type 1 (0/1 in the list)
01/11/2012 15:57:32 Selected Security Scheme 1
01/11/2012 15:57:32 No authentication needed
01/11/2012 15:57:32 VNC authentication succeeded
01/11/2012 15:57:32 Desktop name "kindle:0.0"
01/11/2012 15:57:32 Connected to VNC server, using protocol version 3.8
01/11/2012 15:57:32 VNC server default format:
01/11/2012 15:57:32 8 bits per pixel.
01/11/2012 15:57:32 Colour map (not true colour).
01/11/2012 15:57:32 client2server supported messages (bit flags)
01/11/2012 15:57:32 00: 00ff 0081 0000 0000 - 0000 0000 0000 0000
01/11/2012 15:57:32 08: 0000 0000 0000 0000 - 0000 0000 0000 0000
01/11/2012 15:57:32 10: 0000 0000 0000 0000 - 0000 0000 0000 0000
01/11/2012 15:57:32 18: 0000 0000 0000 0000 - 0000 0000 0000 0004
01/11/2012 15:57:32 server2client supported messages (bit flags)
01/11/2012 15:57:32 00: 001f 0080 0000 0000 - 0000 0000 0000 0000
01/11/2012 15:57:32 08: 0000 0000 0000 0000 - 0000 0000 0000 0000
01/11/2012 15:57:32 10: 0000 0000 0000 0000 - 0000 0000 0000 0000
01/11/2012 15:57:32 18: 0000 0000 0000 0000 - 0000 0000 0000 0004
01/11/2012 15:57:32 Connected to Server "unknown (x11vnc 0.9.13)"
01/11/2012 15:57:32 ZRLE decoding failed (-5)
partially updating eink display (0,0)-(599,799)
01/11/2012 15:57:32 ZRLE decoding failed (-5)
partially updating eink display (0,0)-(599,799)
partially updating eink display (0,0)-(317,417)
partially updating eink display (288,400)-(319,414)
partially updating eink display (288,400)-(319,414)
01/11/2012 15:57:42 Warning: possible ZRLE corruption
partially updating eink display (288,400)-(319,414)
01/11/2012 15:57:42 Warning: possible ZRLE corruption
partially updating eink display (288,400)-(319,414)
01/11/2012 15:57:43 Warning: possible ZRLE corruption
partially updating eink display (288,400)-(319,414)
partially updating eink display (288,400)-(319,414)
partially updating eink display (288,400)-(319,414)
01/11/2012 15:57:44 Warning: possible ZRLE corruption
partially updating eink display (288,400)-(319,414)
partially updating eink display (288,400)-(319,414)
01/11/2012 15:57:44 Warning: possible ZRLE corruption
partially updating eink display (288,400)-(319,414)
01/11/2012 15:57:45 Warning: possible ZRLE corruption
partially updating eink display (288,400)-(319,414)
01/11/2012 15:57:45 Warning: possible ZRLE corruption
partially updating eink display (288,400)-(319,414)
01/11/2012 15:57:45 Warning: possible ZRLE corruption
partially updating eink display (288,400)-(319,414)
partially updating eink display (288,400)-(319,414)
partially updating eink display (288,400)-(319,414)
01/11/2012 15:58:00 Warning: possible ZRLE corruption
|
however - if working - this would present us with the best of all worlds.
EDIT: I had a dig around in the command line switches but nothing leaped out as really useful for further testing. would have to jump into the code.
(/mnt/us/kindlevncviewer/kindlevncviewer --help )
/mnt/us/kindlevncviewer/config.lua appears to be all key related.
so no obvious easy wins.