From: Russell King <rmk@arm.linux.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: zImage now holds vmlinux, System.map and config in sections. (fwd)
Date: Tue, 25 Feb 2003 21:24:57 +0000 [thread overview]
Message-ID: <20030225212457.G21014@flint.arm.linux.org.uk> (raw)
In-Reply-To: <b3gi0e$g2i$1@cesium.transmeta.com>; from hpa@zytor.com on Tue, Feb 25, 2003 at 12:00:14PM -0800
On Tue, Feb 25, 2003 at 12:00:14PM -0800, H. Peter Anvin wrote:
> Followup to: <20030225092520.A9257@flint.arm.linux.org.uk>
> By author: Russell King <rmk@arm.linux.org.uk>
> In newsgroup: linux.dev.kernel
> >
> > On Tue, Feb 25, 2003 at 07:28:46AM +0100, Mikael Starvik wrote:
> > > >I don't know linker scripts very well.
> > > >Can this be done for all architectures?
> > > >I'd like to see a solution that is arch-independent.
> > >
> > > In embedded systems it is probably not desirable to keep
> > > System.map and config in zImage (takes too much valuable space).
> >
> > Agreed - zImage is already around 1MB on many ARM machines, and since
> > loading zImage over a serial port using xmodem takes long enough
> > already, this is one silly feature I'll definitely keep out of the
> > ARM tree.
> >
>
> Isn't that what "strip" is for?
zImage on ARM is a binary blob without any formatting. The first
instruction to be executed is at the start of the file. Perfect
for loading directly into flash or RAM via whatever boot loader
or debugger you choose.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-02-25 21:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 6:28 zImage now holds vmlinux, System.map and config in sections. (fwd) Mikael Starvik
2003-02-25 9:25 ` Russell King
2003-02-25 11:07 ` Ville Herva
2003-02-25 11:35 ` Russell King
2003-02-25 12:03 ` Ville Herva
2003-02-25 14:34 ` Jeremy Jackson
2003-02-26 18:41 ` Peter Bergner
2003-02-25 22:00 ` Bryan Andersen
2003-02-25 12:50 ` Remco Post
2003-02-25 13:35 ` Russell King
2003-02-25 16:38 ` Randy.Dunlap
2003-02-25 17:52 ` Russell King
2003-02-26 20:01 ` Todd Inglett
2003-02-26 20:45 ` Peter Bergner
2003-02-25 19:22 ` Ville Herva
2003-02-25 16:23 ` Randy.Dunlap
2003-02-25 20:00 ` H. Peter Anvin
2003-02-25 21:24 ` Russell King [this message]
2003-02-25 21:52 ` H. Peter Anvin
2003-02-25 23:21 ` Magnus Danielson
[not found] <Pine.LNX.4.33.0302241010200.1088-100000@localhost.localdomain>
2003-02-24 19:58 ` Randy.Dunlap
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=20030225212457.G21014@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=hpa@zytor.com \
--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