Just some bzImage trivia: if you look closely, you will find that it
uses the same compression (gzip) but puts the compressed image in high
memory (above 1M) rather than below the 640K boundary, allowing a much
larger compressed image. Despite the name, it does _not_ use bzip2 for
compression and does _not_ get any better compression.
gvb
At 06:42 PM 3/29/00 -0600, you wrote:
>
> > Hi All,
>
> > While creating the zImage for 2.2.13, I got an error saying
> > "System is too big, try using bzImage". What does this mean ?
>
> > Thanks,
>
> It means exactlly what it says. Try using the command:
>
> make bzImage
>
> ... instead of the 'make zImage' command that you are currently
> trying.
>
> Basically the zImage decompression stub and loading mechanism
> on x86 can't handle an image over a certain size (600K?).
> The decompression stub in bzImage is able to handle a larger
> image, and bzImage gets a bit higher compression to boot.
>Jim
>Dennis [EMAIL PROTECTED]
>Linuxcare: Linux Corporate Support
>Team: http://www.linuxcare.com
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
