Bhaskar, I've never received any email from you, let alone an attachment. I have no idea why. Thanks for sending it, but I guess all explore some other options before trying to get the kdrive X server running.
Craig, I'll look at directvnc. I looked at fbvnc, which is another package for a vnc client. It doesn't require an X11 server, but it does require the regular vnc source tree for build. And the regular vnc source tree requires the X11 libraries, even the vncviewer.
So, I've been assuming a running X11 server isn't required, but the X11 libraries ARE required to build any of the vnc client varieties. Sounds easy, but the Makefiles are set up for cross compiling. And the Vnc build tree uses Imake to dynamically build the Makefiles. Getting vnc to build in a cross-compile enviroment isn't easy, at least for me. Haven't given up, just tabled it until I got the display and X working on the gum. I figured if I got and X server up and running, I could tell if problems with the "custom built" vnc viewer was a result of my Makefile hacks, or simply not understanding how to configure things on the gum.
I did see a binary for fbvnc for arm, so I downloaded and gzip -d 'd it on the gum. But when I try to execute it (e.g. ./fbvnc) I get a message that says that fbvnc is not found. It's definitely there, I see it, and I'm invoking it with a full path name. I tried moving it to a directory in my $PATH variable, but same results. Wierd. Figured I'd have to build it, which brought me back to having to get vnc cross-compiling (since fbvnc requires it).
Maybe I'll bypass TinyX/Kdrive and retry cross-compiling a vnc client first.