From: Henry N. <Hen...@ar...> - 2004-08-01 11:51:45
|
http://home.arcor.de/henryn/sdl_colinux-20040730.zip TESTFB5.EXE: Runs a SDL-Framebuffer-Daemon. This starts with a colour raster and wait than for update flag. SHM_TEST5.EXE: Run this will put many rectangles into shared memory. First quit some informations about shared memory with Enter key. After every rectangle this will set an update bit and update coordinates for rect (only one rect). TESTFB5F.EXE: The same, but ignor rect sizes. Always update full 640x480 area. Here you can verify the performance to TESTFB5.EXE. What do they programs? Are only a simple test, how can I do connect two programs via shared memory under Windows. The SDL-Daemon was compiled from linux with mingw. The SHM_TEST5.C simulate the update-rect from a kernel-FB-Driver in frame buffer memory. Yes, this is all not perfect, but it's my first windows program with shared memory. I have read some helps and do make up to test5. I have not understand all the "virtual", "paged" and so in mailing list. Yes, I know this from some kernel programmings. But in this sample I do not need this. After this sample I think, it's very easy to connect colinux kernel-daemon to a viewer for framebuffer. I am using SDL, because it's my homebase tool for graphics. Please show into my source. Yes, they are not complety perfect and not structured for work in real project. Many constans are hard coded, such video base of 640x480x256 (8 bit) in shared memory. It was compiled under linux SuSE 9.0 (in a colinux box!) and I run this on XP Home. My video settings in XP are 1024x768x32k (16 bit color deph). This sample should everybody help to understand framebuffer, and shared memory problems. It's the beginning for "coLinux graphics" without VNC & Co. Thanks for many ideas in the long ML-thread before! Nice effect: Run 2x TESTFB5.EXE and than SHM_TEST5.EXE ;-) Next? Anybody should be give some samples, how can use dirty bit of MMU! And a implementation of shared memory into colinux kernel. Henry |