From: Scott Wood <scottwood@freescale.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 17/19] bootwrapper: compatibility layer for old U-Boots (a.k.a. cuImage, cuboot)
Date: Wed, 14 Mar 2007 16:48:49 -0500 [thread overview]
Message-ID: <45F86DC1.9010804@freescale.com> (raw)
In-Reply-To: <20070314214805.GA9546@mag.az.mvista.com>
Mark A. Greer wrote:
> Are you sure that '_end' (which is the end of the zImage/cuImage)
> is safe to use? If the kernel is large enough (e.g., INITRAMFS)
> it will overwrite your dtb when its decompressed and relocated to 0.
> You need to grok the elfheader to figure out where the kernel will end
> and take the max of that and _end.
Wouldn't it overwrite the bootwrapper itself before overwriting the heap?
-Scott
next prev parent reply other threads:[~2007-03-14 21:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 20:42 [PATCH 17/19] bootwrapper: compatibility layer for old U-Boots (a.k.a. cuImage, cuboot) Scott Wood
2007-03-12 21:07 ` Kumar Gala
2007-03-13 18:16 ` Scott Wood
2007-03-13 18:50 ` Kumar Gala
2007-03-13 19:01 ` Scott Wood
2007-03-13 19:13 ` Kumar Gala
2007-03-13 19:25 ` Scott Wood
2007-03-12 21:12 ` Kumar Gala
2007-03-13 15:28 ` Scott Wood
2007-03-14 4:25 ` Paul Mackerras
2007-03-14 15:59 ` Scott Wood
2007-03-14 16:08 ` Kumar Gala
2007-03-14 16:45 ` Kim Phillips
2007-03-14 23:36 ` David Gibson
2007-03-15 15:17 ` Scott Wood
2007-03-14 6:35 ` David Gibson
2007-03-14 16:59 ` Scott Wood
2007-03-14 23:56 ` David Gibson
2007-03-15 16:40 ` Scott Wood
2007-03-16 0:09 ` David Gibson
2007-03-14 21:48 ` Mark A. Greer
2007-03-14 21:48 ` Scott Wood [this message]
2007-03-14 23:23 ` Mark A. Greer
2007-03-15 0:04 ` David Gibson
2007-03-15 1:59 ` Mark A. Greer
2007-03-15 2:02 ` David Gibson
2007-03-15 2:05 ` David Gibson
2007-03-15 2:15 ` Mark A. Greer
2007-03-15 2:12 ` Mark A. Greer
2007-03-29 23:12 ` Milton Miller
2007-03-15 0:01 ` David Gibson
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=45F86DC1.9010804@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mgreer@mvista.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).