linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-dev@ozlabs.org, vijay sharma <vjai22@gmail.com>
Subject: Re: PPCboot and latest kernel
Date: Mon, 27 Jul 2009 16:59:01 -0500	[thread overview]
Message-ID: <20090727215901.GA19572@b07421-ec1.am.freescale.net> (raw)
In-Reply-To: <20090720174041.1873A832E416@gemini.denx.de>

On Mon, Jul 20, 2009 at 07:40:41PM +0200, Wolfgang Denk wrote:
> > zImage starting: loaded at 0x01900000 (sp: 0x0fdc3a08)
> > Allocating 0x165ca04 bytes for kernel ...
> > gunzipping (0x00000000 <- 0x0190c000:0x02f58efc)...done 0x1637b54 bytes
> 
> You loaded the image at 01900000, but the uncompr4essed image extends
> until 02f58efc, i. e. there is a good chance that you will overwrite
> parts of the still uncompressed image.

I think the above output says that the compressed image extends to
0x02f58efc, and that the uncompressed image goes from zero to 0x165ca04. 
So no conflict (you should get an error message in case of conflict) with
0x01900000.

> > Linux/PowerPC load:
> > Finalizing device tree... flat tree at 0x2f65300 <== Beyond this point no
> > output is available.
> 
> Your device tree might be wrong, too.

Either that or something is wrong with the kernel itself.  This is the
point at which it transfers control to the main kernel.

-Scott

  reply	other threads:[~2009-07-27 21:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e571380d0907191132u3985423aiacc7ec8c75c0534b@mail.gmail.com>
2009-07-19 18:36 ` PPCboot and latest kernel vijay sharma
2009-07-20 17:40   ` Wolfgang Denk
2009-07-27 21:59     ` Scott Wood [this message]
2009-07-27 22:07   ` Scott Wood

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=20090727215901.GA19572@b07421-ec1.am.freescale.net \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=vjai22@gmail.com \
    --cc=wd@denx.de \
    /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).