[Etherboot-developers] tips re disk on chip, part 3
Brought to you by:
marty_connor,
stefanhajnoczi
|
From: Ken Y. <ke...@nl...> - 2000-11-04 12:29:54
|
Ok, here's what I *think* you have to do: Get those kernel and LILO patches working so that it leaves alone 0x90000 and above. Test by booting a kernel with the modified LILO and kernel. Look at first-linux.S in mknbi-1.0. There is a memory map somewhere in the comments. Note the areas used by Etherboot for loading, notably the kernel parameter area, the bootp area and the block used for the control tags from the first block of the netboot image. A couple of these constants are defined in the Etherboot source, the RELOCADDR in Makefile and the BOOTP buffer address in etherboot.h I think. Shift them down 64k. The rest are in mknbi.pl, the segment constants used by mknbi-linux. Also the segment constant for the control tags. Shift these down to 0x8NNN. Don't use .lzrom images, because the decompressor uses the 0x80000 segment. Get it working with .rom images then hack the decompressor to work from the 0x70000 segment. Naturally you can't load kernels into low memory that are larger than 0x80000. Try bzImages instead then you can have as large a kernel as you want. Maybe this is mandatory for the kernel and LILO patches anyway. Good luck. Let us know how you go. |