From: Wolfgang Denk <wd@denx.de>
To: Alex Zeffertt <ajz@cambridgebroadband.com>
Cc: "Walser, Martin" <mwalser@harris.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: unable to uncompess kernel image
Date: Tue, 05 Feb 2002 17:58:30 +0100 [thread overview]
Message-ID: <20020205165835.AD017116B8@denx.denx.de> (raw)
In-Reply-To: Your message of "Tue, 05 Feb 2002 15:52:24 GMT." <3C5FFFB8.5000409@cambridgebroadband.com>
In message <3C5FFFB8.5000409@cambridgebroadband.com> you wrote:
>
> I'm a little bit confused as to whether you are trying to build a ramdisk image or a kernel image.
Well, as I understood he tried to combine both the kernel and the
ramdisk images in one file; this is sometimes useful when you want to
deal with a single file only (like when booting from a boot server).
In PPCBoot terminology this is called a "multi-file image":
$ mkimage -A ppc -O Linux -T multi -C gzip \
-n 'Linux Multiboot-Image' -e 0 -a 0 \
-d vmlinux.gz:ramdisk_image.gz pMulti
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
A man either lives life as it happens to him, meets it head-on and
licks it, or he turns his back on it and starts to wither away.
-- Dr. Boyce, "The Menagerie" ("The Cage"), stardate unknown
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-05 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 14:56 unable to uncompess kernel image Walser, Martin
2002-02-05 15:52 ` Alex Zeffertt
2002-02-05 16:58 ` Wolfgang Denk [this message]
2002-02-05 16:00 ` Wolfgang Denk
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=20020205165835.AD017116B8@denx.denx.de \
--to=wd@denx.de \
--cc=ajz@cambridgebroadband.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mwalser@harris.com \
/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;
as well as URLs for NNTP newsgroup(s).