From: Darius Augulis <augulis.darius@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] IXP425 TEXT_BASE
Date: Tue, 04 Aug 2009 17:34:42 +0300 [thread overview]
Message-ID: <4A784702.40806@gmail.com> (raw)
In-Reply-To: <20090804134901.5C0488340728@gemini.denx.de>
On 08/04/2009 04:49 PM, Wolfgang Denk wrote:
> Dear Darius Augulis,
>
> In message<4A78342C.5090307@gmail.com> you wrote:
>> usually TEXT_BASE is offset, which size depends on your requirements for
>
> No. TEXT_BASE is an absolute address.
yes, but depends on the physical RAM base and size.
>
>> stack size and memory size for malloc. If your DRAM base is 0x0 and
>> TEXT_BASE is 0xf80000, you will have almost 16Mb for stack and malloc
>> and your u-boot code will be linked and loaded to 0xf80000 address.
>> 16Mb is probably too much, or your DRAM base is not 0x0.
>
> On architectures like ARM (where the implementation is based on a
> broken concept of the system memory map) TEXT_BASE should always be
> chosen to be as high as possible to put the ("relocated") U-Boot code
> as close as possible to the very end of available RAM. For systems
> with several RAM size options you have to set this according to the
> smallest possible RAM size, of course (which is a major PITA).
could you please explain more? why to the end of RAM?
for example I have 16MB RAM, base is 0x10000000. TEXT_BASE = 0x10400000.
Why is better to set this to 0x10F00000 ? To have more stack and malloc
memory? But U-boot will never exceed such limit? Please explain where I
am wrong. Thanks!
Darius A.
>
>
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2009-08-04 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 11:59 [U-Boot] IXP425 TEXT_BASE Teh Kok How
2009-08-04 13:14 ` Darius Augulis
2009-08-04 13:49 ` Wolfgang Denk
2009-08-04 14:34 ` Darius Augulis [this message]
2009-08-04 15:57 ` Wolfgang Denk
2009-08-05 3:22 ` Teh Kok How
2009-08-05 6:38 ` Teh Kok How
2009-08-05 7:48 ` 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=4A784702.40806@gmail.com \
--to=augulis.darius@gmail.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 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.