转载时请注明出处和作者联系方式:http://blog.csdn.net/mimepp
作者联系方式:YU TAO <yut616 at sohu dot com>
看到一个 MicroXwin 系统,架构很适合嵌入系统,这里做个记录。
http://www.microxwin.com
国内好象不能直接访问,需要找些代理,或其他工具来访问。
MicroXwin implements graphics processing in the kernel as a load module and provides a character driver interface to the associated X11 library.
空间占用小:
不过商用有 license 问题。
作者联系方式:YU TAO <yut616 at sohu dot com>
看到一个 MicroXwin 系统,架构很适合嵌入系统,这里做个记录。
http://www.microxwin.com
国内好象不能直接访问,需要找些代理,或其他工具来访问。
MicroXwin implements graphics processing in the kernel as a load module and provides a character driver interface to the associated X11 library.
- MicroXwin is binary compatible to the Xlib API.
- However it is neither client server nor network oriented. Graphics operations are implemented in
- the linux kernel via a kernel module.
- An open source Xlib library sends graphics commands to the kernel.
- There is no network overhead and no context switch from X client to X server.
- This makes our solution smaller and faster than traditional X Windows.
- The storage and run-time memory requirements for MicroXwin is much lower than Xorg server.
- The sizes of the main compoenents for x86 are:
- LibX11.so is 720K bytes.
- LibXext.so is 7K bytes.
- Kernel module x11.ko is 200K bytes.
- The Xorg server has a disk footprint of 1.8MB with run time memory usage of 12MB.
- This is much higher than the roughly 300Kbytes of kernel memory used by the kernel module.
- Besides that MicroXwin does all bitmap rendering in the kernel and needs only a small set
- of SNF fonts. The smallest MicroXwin distribution can fit within ~ 1MB of disk space.