7cf32cad15
* Start threads with IRQs enabled. * Move symbol exports to arch specific file. * Prepare for real command line in the future. * Handle csum for partition that crosses flash boundary. * Set utsname. Signed-off-by: Mikael Starvik <starvik@axis.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org> |
||
---|---|---|
.. | ||
decompress.ld | ||
head.S | ||
Makefile | ||
misc.c | ||
README |
Creation of the self-extracting compressed kernel image (vmlinuz) ----------------------------------------------------------------- $Id: README,v 1.1 2001/12/17 13:59:27 bjornw Exp $ This can be slightly confusing because it's a process with many steps. The kernel object built by the arch/etrax100/Makefile, vmlinux, is split by that makefile into text and data binary files, vmlinux.text and vmlinux.data. Those files together with a ROM filesystem can be catted together and burned into a flash or executed directly at the DRAM origin. They can also be catted together and compressed with gzip, which is what happens in this makefile. Together they make up piggy.img. The decompressor is built into the file decompress.o. It is turned into the binary file decompress.bin, which is catted together with piggy.img into the file vmlinuz. It can be executed in an arbitrary place in flash. Be careful - it assumes some things about free locations in DRAM. It assumes the DRAM starts at 0x40000000 and that it is at least 8 MB, so it puts its code at 0x40700000, and initial stack at 0x40800000. -Bjorn