All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geir Thomassen <chaos@in.fer.no>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Memory layout on PXA
Date: Wed, 12 Feb 2003 19:40:27 +0100	[thread overview]
Message-ID: <3E4A951B.5030309@in.fer.no> (raw)

I am porting u-boot to a custom PXA255 board.

Just a quick check, to see if I understand the code correctly:

1) u-boot is copied from flash into memory at TEXT_BASE
(typ. 0xA3000000 on PXA).

2) The stack is below the u-boot code. From cpu/xscale/start.S,
it looks like the stack is at TEXT_BASE - CFG_MALLOC_LEN - 12. I
think the stack grows toward lower addresses on arm, is this
correct ?

3) Memory for malloc() is supposed to be after the u-boot
code (including initialized and initialized data) at address
armboot_real_end. If I understand the code correct, it points
0xbadc0de. Some time, it has been set to armboot_end +
CONFIG_STACKSIZE in cpu/xscale/cpu.c, but the code for doing
so have been commented out (both in 0.2.0 and in CVS). There
is room for putting the heap between the stack and the u-boot
code ...

Sooo, if I understand this correct, this is a mess. How
should it be done ? Are there any good reasons for a particular
memory layout on PXA ?

BTW: Does u-boot run "out of the box" on any PXA hardware, I
don't understand how it could unless the hardware have RAM at
0xBADC0DE ..

-- 
Geir

             reply	other threads:[~2003-02-12 18:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 18:40 Geir Thomassen [this message]
2003-02-12 19:07 ` [U-Boot-Users] Memory layout on PXA Robert Schwebel
2003-02-12 20:08   ` Wolfgang Denk
2003-02-13  6:38     ` Robert Schwebel
2003-02-13  6:40     ` 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=3E4A951B.5030309@in.fer.no \
    --to=chaos@in.fer.no \
    --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.