Re: [cobalt-developers] Raq3 kernel and dev86

[Chris Johnson <cjohnson@xxxxxxxxxxxxx>]

	> From   : Tim Hockin <thockin@xxxxxxxxxx>
	> Reply  : cobalt-developers@xxxxxxxxxxxxxxx
	> 
	> Subject: Re: [cobalt-developers] Raq3 kernel and dev86
	> 
	> Lastly, re: kernel size and a Cobalt system:  it shouldn't
	> matter how big the kernel image gets - because we don't use
	> the standard mechanism for booting.  By the time we actually
	> read the kernel from disk we are in protected mode, and we
	> don't need to worry about 640k.  If you got an error from the
	> compile about size, please send me the output of the compile.
	> 'make vmlinux' should not be checking size, because at that
	> point it is irrelevant.

    There is one nit here.  If you want to use gdb on
    the resulting kernel, it is important to strip the
    kernel before you try to boot it.

    Our ROM code has a space of 2 Meg for the gzip'ed
    kernel.  A full kernel with many static modules can
    exceed that size when the symbol table is included.

	% strip -o bootkern vmlinux
	% gzip bootkern

    Then point gdb at the original vmlinux so it can
    find the symbol table.

    cj*