public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [rfc] warning about overlapping regions whenbooting with bootm
Date: Sun, 17 Feb 2008 23:09:08 +0100	[thread overview]
Message-ID: <20080217220908.CC54924544@gemini.denx.de> (raw)
In-Reply-To: Your message of "Sun, 17 Feb 2008 15:29:23 EST." <200802171529.23434.rgetz@blackfin.uclinux.org>

In message <200802171529.23434.rgetz@blackfin.uclinux.org> you wrote:
>
> I always thought that when decompressing a uImage, that the entry point was 
> stored in the header, (at the beginning of the file) and was read after the 
> decompression took place - is that wrong?

I'm not sure what all the different architectures do,  but  at  least
for PowerPC, ARM and MIPS I know that one of the very first things we
do in the bootm code is to create a local copy of the image header.

Search for 'memcpy.*header'.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
You can do this in a number of ways.     IBM chose to do all of them.
Why do you find that funny?        -- D. Taylor, Computer Science 350

  reply	other threads:[~2008-02-17 22:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16  7:59 [U-Boot-Users] [rfc] warning about overlapping regions when booting with bootm Mike Frysinger
2008-02-16 23:06 ` Wolfgang Denk
2008-02-16 23:19   ` Mike Frysinger
2008-02-17 20:29   ` [U-Boot-Users] [rfc] warning about overlapping regions whenbooting " Robin Getz
2008-02-17 22:09     ` Wolfgang Denk [this message]
2008-02-17 22:55       ` Robin Getz
2008-02-22 17:49       ` Marian Balakowicz

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=20080217220908.CC54924544@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.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