From: Wakko Warner <wakko@animx.eu.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: zImage on 2.6?
Date: Tue, 3 May 2005 06:45:03 -0400 [thread overview]
Message-ID: <20050503104503.GA11123@animx.eu.org> (raw)
In-Reply-To: <20050502193503.20e6ac6e.rddunlap@osdl.org>
Randy.Dunlap wrote:
> On Mon, 2 May 2005 21:29:51 -0400 Wakko Warner wrote:
> | Is it possible to use zImage on 2.6 kernels or is bzImage required?
>
> What processor architecture?
x86. Does zImage work on other arches? (I've only ever dealt with alpha
and sparc other than x86)
> It's supported in arch/i386/Makefile (and some others).
> For i386, you'll need to disable enough (lots of) options to make the
> resulting output file small enough...
The resultant bzImage is ~760kb. I compiled out everything I could, only
ram disk/initrd, and ext2 are compiled in.
If you'd like to see the .config, I'll send it up.
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2005-05-03 10:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 1:29 zImage on 2.6? Wakko Warner
2005-05-03 2:35 ` Randy.Dunlap
2005-05-03 10:45 ` Wakko Warner [this message]
2005-05-03 14:26 ` Randy.Dunlap
2005-05-03 16:33 ` Wakko Warner
2005-05-03 16:59 ` Randy.Dunlap
2005-05-03 22:19 ` Wakko Warner
2005-05-03 22:27 ` segin
2005-05-03 22:31 ` Wakko Warner
2005-05-03 23:15 ` segin
2005-05-04 0:28 ` shogunx
2005-05-04 1:29 ` Wakko Warner
2005-07-12 4:55 ` H. Peter Anvin
2005-05-03 22:37 ` Randy.Dunlap
2005-05-03 23:05 ` Wakko Warner
2005-05-03 23:16 ` Randy.Dunlap
2005-07-12 4:54 ` H. Peter Anvin
2005-05-03 18:28 ` Krzysztof Halasa
2005-07-12 4:58 ` H. Peter Anvin
2005-05-03 16:06 ` Rick Warner
2005-05-03 16:40 ` Wakko Warner
2005-05-03 18:01 ` Lennart Sorensen
2005-05-03 18:44 ` Brian Gerst
2005-05-03 22:20 ` Wakko Warner
2005-05-03 21:42 ` Rick Warner
2005-05-03 22:23 ` Wakko Warner
2005-07-12 5:00 ` H. Peter Anvin
2005-05-04 13:50 ` Wakko Warner
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=20050503104503.GA11123@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.