From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: [PATCH][CFT] bring ARM memory layout in line with the documented behaviour
Date: Mon, 27 Oct 2003 16:05:23 +0100 [thread overview]
Message-ID: <3F9D3433.4060809@imc-berlin.de> (raw)
In-Reply-To: <20030918110044.6595DC59E4@atlas.denx.de>
Hi,
I am confused about ARM and the use of TEXT_BASE:
Anders Larsen wrote:
> Memory layout example based on my PXA255 (TEXT_BASE = 0xA07E0000):
>
> 0xA079FF74 Monitor Stack (growing downwards)
> 0xA079FF80 Board Info Data and permanent copy of Global Data
> 0xA07A0000 Malloc Arena
> 0xA07E0000 RAM copy of Monitor Code
> ... optional: Frame Buffer
> 0xA07FFFFF [End of RAM]
Wolfgang Denk wrote:
> TEXT_BASE determines the start address in FLASH memory which is used
> before relocation.
Now is TEXT_BASE the "address in FLASH memory" or the address of the "RAM copy
of Monitor Code"???
Thanks!
Steven
next prev parent reply other threads:[~2003-10-27 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 14:35 [U-Boot-Users] [PATCH][CFT] bring ARM memory layout in line with the documented behaviour Anders Larsen
2003-09-18 11:00 ` [U-Boot-Users] " Wolfgang Denk
2003-09-18 12:15 ` Anders Larsen
2003-09-18 21:20 ` Wolfgang Denk
2003-10-13 16:10 ` [U-Boot-Users] Re: [PATCH][CFT] bring ARM memory layout in line with the documentation Anders Larsen
2003-10-13 16:16 ` Robert Schwebel
2003-10-13 16:40 ` Wolfgang Denk
2003-10-14 7:55 ` Anders Larsen
2003-10-14 20:30 ` Wolfgang Denk
2003-10-16 9:56 ` Robert Schwebel
2003-10-16 10:31 ` Wolfgang Denk
2003-10-16 10:50 ` Robert Schwebel
2003-10-16 11:21 ` Wolfgang Denk
2003-10-27 15:05 ` Steven Scholz [this message]
2003-10-27 16:02 ` Anders Larsen
2003-12-06 16:08 ` [U-Boot-Users] [PATCH][CFT] bring ARM memory layout in line with the documented behaviour Wolfgang Denk
2003-12-07 8:37 ` Robert Schwebel
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=3F9D3433.4060809@imc-berlin.de \
--to=steven.scholz@imc-berlin.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 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.