From: Matthias Kaehlcke <matthias@kaehlcke.net>
To: "Eric Bénard" <eric@eukrea.com>
Cc: barebox@lists.infradead.org
Subject: Re: confusion about relocation (ARM)
Date: Fri, 1 Jan 2010 22:48:26 +0100 [thread overview]
Message-ID: <20100101214826.GS5093@darwin> (raw)
In-Reply-To: <4B3E5CCD.60400@eukrea.com>
hi eric,
thanks for your reply
El Fri, Jan 01, 2010 at 09:36:29PM +0100 Eric Bénard ha dit:
> Le 01/01/2010 20:48, Matthias Kaehlcke a écrit :
>> a comment in start_barebox() says 'We are running from RAM now', so i
>> deduced SDRAM must work. but after having a look at start-arm.S i'm a
>> little bit confused. as far as i understand the barebox code is copied
>> to RAM in copy_loop(). what i don't see is where the program counter
>> is set to the address in RAM?
>>
> in arch/arm/cpu/start-arm.S @ line 245 :
> ldr pc, _start_armboot
i saw this line, but i don't understand how it comes that
the address at _start_armboot points to RAM and not to the flash.
another question: how does ARCH_TEXT_BASE fit in here? i defined it as
0x05700000, but in the barebox image _TEXT_BASE is 0x00000000
kind regards
--
Matthias Kaehlcke
Embedded Linux Developer
Barcelona
You must have a plan. If you don't have a plan,
you'll become part of somebody else's plan
.''`.
using free software / Debian GNU/Linux | http://debian.org : :' :
`. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-01-01 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 19:48 confusion about relocation (ARM) Matthias Kaehlcke
2010-01-01 20:36 ` Eric Bénard
2010-01-01 21:48 ` Matthias Kaehlcke [this message]
2010-01-04 12:07 ` Sascha Hauer
2010-01-04 19:21 ` Matthias Kaehlcke
2010-01-04 20:13 ` Robert Schwebel
2010-01-04 21:10 ` Matthias Kaehlcke
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=20100101214826.GS5093@darwin \
--to=matthias@kaehlcke.net \
--cc=barebox@lists.infradead.org \
--cc=eric@eukrea.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.