All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Calaby <julian.calaby@gmail.com>
To: Frans Pop <elendil@planet.nl>,
	sparclinux@vger.kernel.org, linux-kbuild@vger.kernel.org,
	Jurij Smakov <jurij@wooyd.org>,
	David Miller <davem@davemloft.net>
Subject: Re: [PATCH,resend] sparc64: build compressed image (zImage) by default
Date: Fri, 17 Jul 2009 09:42:15 +1000	[thread overview]
Message-ID: <646765f40907161642u4d7bb2fo1e4d3a682acf7958@mail.gmail.com> (raw)
In-Reply-To: <20090716201601.GA6038@merkur.ravnborg.org>

On Fri, Jul 17, 2009 at 06:16, Sam Ravnborg<sam@ravnborg.org> wrote:
> 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.
>
> Could we agree on the _same_ format for zImage on sparc and sparc64 and then apply that patch?
>
> I know Julian is working on unifying piggyback_{32,64}.c so maybe that is
> covered by his work?

I have been fiddling with that, but time is been at a premium at the moment.

I don't believe that changes to the zImage / vmlinux targets will
affect this as the tftpboot code uses the uncompressed (I believe)
"Image" target.

Thanks,

-- 

Julian Calaby

Email: julian.calaby@gmail.com
.Plan: http://sites.google.com/site/juliancalaby/

WARNING: multiple messages have this Message-ID (diff)
From: Julian Calaby <julian.calaby@gmail.com>
To: Frans Pop <elendil@planet.nl>,
	sparclinux@vger.kernel.org, linux-kbuild@vger.kernel.org,
	Jurij Smakov <jurij@wooyd.org>,
	David Miller <davem@davemloft.net>
Subject: Re: [PATCH,resend] sparc64: build compressed image (zImage) by
Date: Thu, 16 Jul 2009 23:42:15 +0000	[thread overview]
Message-ID: <646765f40907161642u4d7bb2fo1e4d3a682acf7958@mail.gmail.com> (raw)
In-Reply-To: <20090716201601.GA6038@merkur.ravnborg.org>

On Fri, Jul 17, 2009 at 06:16, Sam Ravnborg<sam@ravnborg.org> wrote:
> 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.
>
> Could we agree on the _same_ format for zImage on sparc and sparc64 and then apply that patch?
>
> I know Julian is working on unifying piggyback_{32,64}.c so maybe that is
> covered by his work?

I have been fiddling with that, but time is been at a premium at the moment.

I don't believe that changes to the zImage / vmlinux targets will
affect this as the tftpboot code uses the uncompressed (I believe)
"Image" target.

Thanks,

-- 

Julian Calaby

Email: julian.calaby@gmail.com
.Plan: http://sites.google.com/site/juliancalaby/

  reply	other threads:[~2009-07-16 23:42 UTC|newest]

Thread overview: 18+ 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 18:41 ` Frans Pop
2009-07-16 20:16 ` Sam Ravnborg
2009-07-16 20:16   ` [PATCH,resend] sparc64: build compressed image (zImage) by Sam Ravnborg
2009-07-16 23:42   ` Julian Calaby [this message]
2009-07-16 23:42     ` Julian Calaby
2009-07-22 17:07   ` [PATCH,resend] sparc64: build compressed image (zImage) by default Frans Pop
2009-07-22 17:07     ` Frans Pop
2009-07-22 18:25     ` David Miller
2009-07-22 18:25       ` [PATCH,resend] sparc64: build compressed image (zImage) by David Miller
2009-07-16 20:16 ` [PATCH,resend] sparc64: build compressed image (zImage) by default David Miller
2009-07-16 20:16   ` [PATCH,resend] sparc64: build compressed image (zImage) by David Miller
2009-07-16 21:46   ` [PATCH,resend] sparc64: build compressed image (zImage) by default Frans Pop
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-07-23 18:55   ` Frans Pop
2009-08-17  1:22   ` David Miller
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=646765f40907161642u4d7bb2fo1e4d3a682acf7958@mail.gmail.com \
    --to=julian.calaby@gmail.com \
    --cc=davem@davemloft.net \
    --cc=elendil@planet.nl \
    --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 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.