: Is emulating Frame Buffers just on a memory array (for headless system)
: just "no problem" ?
Yep, no problem. The newer architecture allows the entire nano-X
system to run using a memory framebuffer. This is, in fact, how
the new X11 driver works. The X11 driver allocates some memory
that serves as the framebuffer, and tells the open routine what
format the pixels are, and then all drawing occurs to this memory
area. There is a normally unused driver entry point, Update(),
which then is called back, and the X11 driver updates the X11
display from the memory contents.
I will soon be writing an actual "memory" display driver that will
work similarly, but the Update routine will keep an update region
(dirty rectangle list) instead of doing anything. The memory
and rectangle list could then be used as the basis for a VNC
port, or other method of getting the "framebuffer" data off the target.
The new FBE (framebuffer emulator) could also be useful -
it just mmaps a shared memory segment and displays it from
another process. The current FBE implementation completely
works on X11, but I haven't yet ripped out the mouse and
keyboard handling, so that essentially a headless version of
nano-X could completely run on a desktop, with a seperate
process handling all emulated i/o.
: Full ("official") VNX and/or NX support for this would be great and does
: not seem "far way".
What do you mean by VNX support?
Regards,
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: nanogui-unsubscr...@linuxhacker.org
For additional commands, e-mail: nanogui-h...@linuxhacker.org
