From: Tom Gall <tom_gall@vnet.ibm.com>
To: Samium Gromoff <_deepfire@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is bzImage container large enough?
Date: Sat, 01 Sep 2001 15:41:41 -0500 [thread overview]
Message-ID: <3B914805.F9883E5E@vnet.ibm.com> (raw)
In-Reply-To: <22500.999376181@ocs3.ocs-net>
Keith Owens wrote:
> On Sat, 1 Sep 2001 16:28:06 +0000 (UTC),
> Samium Gromoff <_deepfire@mail.ru> wrote:
> > If one wanting to turn on virtually every kernel CONFIG_* option
> > in order to check if the kernel compiles and then report possible
> > gcc errors to lkml, will the resulting kernel fit the bzImage format?
>
> No, it is far too big.
We just "fixed" this sort of problem for ppc64 the other day. Course we
don't use bzImages but rather zImages but none the less it was still
anoying since we can boot zImages over the network and
of course that makes it quite reasonable to blow past the 1.44
floppy limitation. The bug we fixed was that an uncompressed
kernel could only be up to 4 meg in size, if it was larger, at
uncompression time you'd just lose everything past the 4M mark.
Todd Inglett raised the limit to 8 meg for us, and that's a mighty
large penguin....
Regards,
Tom
--
Tom Gall - PPC64 Code Monkey "Where's the ka-boom? There was
Linux Technology Center supposed to be an earth
(w) tom_gall@vnet.ibm.com shattering ka-boom!"
(w) 507-253-4558 -- Marvin Martian
(h) tgall@rochcivictheatre.org
http://www.ibm.com/linux/ltc/projects/ppc
next prev parent reply other threads:[~2001-09-01 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-01 16:28 is bzImage container large enough? Samium Gromoff
2001-09-01 20:29 ` Keith Owens
2001-09-01 20:41 ` Tom Gall [this message]
2001-09-01 23:49 ` Anton Blanchard
2001-09-01 20:42 ` Mike Castle
2001-09-01 20:49 ` Keith Owens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B914805.F9883E5E@vnet.ibm.com \
--to=tom_gall@vnet.ibm.com \
--cc=_deepfire@mail.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox