public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: sparclinux@vger.kernel.org, linux-kbuild@vger.kernel.org
Cc: Jurij Smakov <jurij@wooyd.org>, David Miller <davem@davemloft.net>
Subject: Re: [PATCH,resend] sparc64: build compressed image (zImage) by default
Date: Wed, 22 Jul 2009 19:07:39 +0200	[thread overview]
Message-ID: <200907221907.40698.elendil@planet.nl> (raw)
In-Reply-To: <20090716201601.GA6038@merkur.ravnborg.org>

On Thursday 16 July 2009, Sam Ravnborg wrote:
> On Thu, Jul 16, 2009 at 08:41:52PM +0200, Frans Pop wrote:
> > From: Jurij Smakov <jurij@wooyd.org>
> > Subject: sparc64: build compressed image (zImage) by default
> >
> > Besides creating the uncompressed vmlinux image for sparc64, also
> > create a compressed zImage. This is more consistent with other
> > architectures and required to make the 'deb-pkg' target work.
> >
> > Signed-off-by: Jurij Smakov <jurij@wooyd.org>
> > Signed-off-by: Frans Pop <elendil@planet.nl>
>
> Hmmm..
> This path does the following:
> 1) zImage becomes default for sparc and sparc64
> 2) fixes zImage on sparc64 (it dod not work before)
> 3) On sparc zImage is a stripped version of vmlinux, on sparc64 it is a
> gzipped not-stripped version of vmlinux - so it introduces a
> significantly different zImage.

If I read arch/sparc/boot/Makefile correctly then the sparc64 image _is_ 
stripped as the zImage target calls $(obj)/image which does the strip.
So the difference is less than you suggest.

> Could we agree on the _same_ format for zImage on sparc and sparc64 and
> then apply that patch?

I vaguely recall from Debian work that loading compressed kernels caused 
problems on sparc32 hardware (due to insufficient memory?), which could 
justify the difference. But I may be wrong.

Cheers,
FJP

  parent reply	other threads:[~2009-07-22 17:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 18:41 [PATCH,resend] sparc64: build compressed image (zImage) by default Frans Pop
2009-07-16 20:16 ` Sam Ravnborg
2009-07-16 23:42   ` Julian Calaby
2009-07-22 17:07   ` Frans Pop [this message]
2009-07-22 18:25     ` David Miller
2009-07-16 20:16 ` David Miller
2009-07-16 21:46   ` Frans Pop
2009-07-23 18:55 ` [PATCH] sparc64: list zImage build target in 'make help' output Frans Pop
2009-08-17  1:22   ` David Miller

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=200907221907.40698.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=davem@davemloft.net \
    --cc=jurij@wooyd.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=sparclinux@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