"BUILD ENVIRONMENT

The Makefile ought to contain everything you need to build the bootimage. For hacking, an optional script "please" helps you do things with the kernel tree. [...]

The toolchain is based on uClibc - http://www.uclibc.org/ [...]

RAMDISKIMAGE USAGE

The ramdisk that is built by this Makefile has the following usage:
* lots of functions are defined in /etc/functions -- see by yourself
* you may add your own additional functions in /etc/functions.local
* Use "standalone" to configure linux for standalone usage with the ramdisk.
* Use "rootfs" to chain-boot into your first Linux partition on CF.
* The ramdisk will automatically attempt to "rootfs" at startup, unless you
create a file or directory named "noautomount" in your WinCE partition.
* We have mkfs.minix and fsck.minix in busybox. No ext2 support, sorry.
To build an ext2 filesystem, you'll have to use a CF reader on your PC,
or to NFS mount a filesystem with your ext2 utilities.
* Busybox is packed up with lots of functionality. Check it out!
* To free the memory occupied by the ramdisk, your rootfs will need to run
the program blockdev, which is part of the util-linux debian package.

* With kernel 2.6, you must use cat /proc/modules instead of lsmod"

http://cvs.sf.net/viewcvs.py/jornada820/bootimage

http://cvs.sf.net/viewcvs.py/jornada820/bootimage/README