From: Wolfgang Denk <wd@denx.de>
To: Steven Hanley <sjh@wibble.net>
Cc: Rolf Liu <rolfl@sc23.sc.mcel.mot.com>,
Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: problem with compressing the kernel
Date: Wed, 28 Jun 2000 09:33:47 +0200 [thread overview]
Message-ID: <200006280733.JAA27847@denx.local.net> (raw)
In-Reply-To: Your message of "Wed, 28 Jun 2000 16:19:12 +1000." <395998E0.65DD0D9B@wibble.net>
In message <395998E0.65DD0D9B@wibble.net> Steven Hanley wrote:
>
> you seem to be confused anyway, yes the kernel is compressed for x86
> machiens (it is however not compressed for other architectures, my ppc
> box uses a normal uncompresased vmlinux image.
Well, on the (embedded) PowerPC systems we are running we use
compressed kernel images - saving lots of space in expensive FLASH
memory is reason enough.
> wheras a kernel image (for ppc) will look like
>
> [17:18:53] 1 innuendo sjh ~>file /mac/System\ Folder/Linux\
> Kernels/vmlinux-2.2.15pre14
> /mac/System Folder/Linux Kernels/vmlinux-2.2.15pre14: ELF 32-bit MSB
> executable, PowerPC or cisco 4500, version 1, statically linked, not
> stripped
This is what you see. Bat some things look different from what they
really are.
I see this:
-> file linux-2.2.13/arch/ppc/mbxboot/zvmlinux
linux-2.2.13/arch/ppc/mbxboot/zvmlinux: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1, statically linked, not stripped
Nevertheless, this file _contains_ a compressed (gzipped) Linux
kernel image as a special section "image":
-> powerpc-linux-objdump -h linux-2.2.13/arch/ppc/mbxboot/zvmlinux
linux-2.2.13/arch/ppc/mbxboot/zvmlinux: file format elf32-powerpc
Sections:
Idx Name Size VMA LMA File off Algn
0 .text 00004a90 00100000 00100000 00010000 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
1 .rodata 000006a0 00104a90 00104a90 00014a90 2**4
CONTENTS, ALLOC, LOAD, READONLY, DATA
2 .data 0000031c 00106000 00106000 00016000 2**2
CONTENTS, ALLOC, LOAD, DATA
3 .bss 000031fc 00107000 00107000 00017000 2**2
ALLOC
4 image 0005d3f8 00000000 00000000 00017000 2**0
CONTENTS, READONLY
> which is a plain all ordinary elf binary pretty much
>
> the compressed kernels found on x86 boxes will look like
There are more things in heaven and earth, Steven, / Than are dreamt
of in your philosophy. :-)
> it may seem you can just gzip an uncompressed vmlinux and get a vmlinuz
> that will boot, except if you notice the devel image just there is not a
> gzip file. There is some executable code added on the front of the image
> so the x86 box will run it on boot up, some of this code uncompresses
> the image.
Same on (embedded) PowerPC
> Now of course I wonder why you would need the ability as after all a
> linux box is all you need to compile and make the image, or heck a
There are systems which are too slow and/or too limited to compile a
kernel (especially embedded systems).
> And of course remember you dont need otr use compressed images on ppc
> machines.
You do, in some cases.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Do not follow where the path may lead....go instead where there is no
path and leave a trail.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-28 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 3:49 problem with compressing the kernel Rolf Liu
2000-06-28 6:19 ` Steven Hanley
2000-06-28 7:33 ` Wolfgang Denk [this message]
2000-06-28 7:55 ` Gregorio Gervasio Jr.
2000-06-28 9:05 ` Gabriel Paubert
2000-06-28 11:45 ` Steven Hanley
2000-06-28 12:27 ` Gabriel Paubert
2000-06-28 12:43 ` Steven Hanley
2000-06-28 12:41 ` Wolfgang Denk
2000-06-28 12:18 ` Tony Mantler
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=200006280733.JAA27847@denx.local.net \
--to=wd@denx.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rolfl@sc23.sc.mcel.mot.com \
--cc=sjh@wibble.net \
/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).