|
Hello.
I am using tinyXserver to port to non-Linux
system.
In TinyXserver the Linux frame-buffer is used. In linux,
mmap function is used to map the memory of framebuffer and this is done
in hw/kdrive/fbdev/fedev.c. When write data to the screen,
the data should be filled to the framebuffer. The
system I am using now has a function for obtaining a framebuffer (array). We
assign this instead of using mmap. We assume (after setting up data
structures) that xserver should make updates to this framebuffer (array) we
receive from our system.
In our system there is a callback to sync timing with display
and we just need to call one function to have the system update display based on
contents of the framebuffer (send array data to display).. I understand our
framebuffer data is supposed to be read and the data supposed to be
displayed continuosly.
My questions:
1. I cannot find which module (section of code/file) xserver
uses to write data to the framebuffer after Pixblit routines. Where
exactly does xserver write to framebuffer array?
2. If we execute TinyXserver only in Linux, a gray screen
is shown. From observing behavior on Linux, when no client is
running, we believe for our system a default gray screen should be filled to the
framebuffer too. I don't know when this implemetation is done. Does anyone
know where the greyscreen data is written to framebuffer?
I appreciate any help with my questions.
Thank you,
M.N |
