public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] arm920t RAM relocation broken?
Date: Fri, 7 Mar 2008 01:03:43 +0100	[thread overview]
Message-ID: <059001c87fee$fe1a7570$030514ac@atmel.com> (raw)
In-Reply-To: 47D05C81.50200@videon-central.com

----- Original Message ----- 
From: "Cory T. Tusar" <ctusar@videon-central.com>
To: <u-boot-users@lists.sourceforge.net>
Cc: <peter.pearse@arm.com>
Sent: Thursday, March 06, 2008 10:05 PM
Subject: [U-Boot-Users] arm920t RAM relocation broken?


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Commit d4fc6012 added an #ifdef CONFIG_AT91RM9200 construct around the
> RAM relocation bits in cpu/arm920t/start.S.  More directly, it added an
> entire secondary relocation snippet surrounded by an 
> #ifdef CONFIG_BOOTBINFUNC construct.
> 
> It appears that this second implementation was later removed in commit
> 80767a6c, but the #ifdef CONFIG_AT91RM9200 logic was not removed also.
> 
> Is RAM relocation only intended to function on at91rm9200 boards, or
> shall I submit a patch fixing the above?
> 
> - -Cory
> 


Does this mean that the AT91RM9200 always relocates?
Then the code is simply wrong.

If you run from a serial flash, then the code is already relocated
and is executing from SDRAM at this point, so the code will crash.


Best Regards
Ulf Samuelsson

  reply	other threads:[~2008-03-07  0:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 21:05 [U-Boot-Users] arm920t RAM relocation broken? Cory T. Tusar
2008-03-07  0:03 ` Ulf Samuelsson [this message]
2008-03-07 19:02   ` Cory T. Tusar

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='059001c87fee$fe1a7570$030514ac@atmel.com' \
    --to=ulf@atmel.com \
    --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