From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] 85xx: Ensure BSS segment isn't linked at address 0
Date: Thu, 08 Oct 2009 00:34:29 +0200 [thread overview]
Message-ID: <20091007223429.290F5E95FA9@gemini.denx.de> (raw)
In-Reply-To: <1254933900-16859-1-git-send-email-ptyser@xes-inc.com>
Dear Peter Tyser,
In message <1254933900-16859-1-git-send-email-ptyser@xes-inc.com> you wrote:
> When U-Boot is relocated from flash to RAM pointers are modified
> accordingly. However, pointers initialzed with NULL values should not
> be modified so that they maintain their intended NULL value. If the
> BSS segment is linked at address 0 its address will not be
> updated as necessary during relocation.
>
> This is a temporary workaround. The end goal is to add support to
> U-Boot to dynamically locate the BSS at an arbitrary address at
> runtime. When the ability to fixup the BSS inteligently is
> added, this workaround can be removed and the 85xx link script
> can put the BSS at a fixed address at link time.
>
> Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
> ---
> Changes since v1:
> - Updated commit title and description
> - Cleaned up logic to determine if we need to fixup bss address
>
> cpu/mpc85xx/u-boot.lds | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
Applied to "reloc" branch, thanks.
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
Save yourself! Reboot in 5 seconds!
next prev parent reply other threads:[~2009-10-07 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 16:45 [U-Boot] [PATCH v2] 85xx: Ensure BSS segment isn't linked at address 0 Peter Tyser
2009-10-07 22:34 ` Wolfgang Denk [this message]
2009-10-08 2:47 ` Kumar Gala
2009-10-08 2:55 ` Stefan Roese
2009-10-08 6:03 ` Wolfgang Denk
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=20091007223429.290F5E95FA9@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