From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 5/7] imx6: add some flexibility for defining macros
Date: Wed, 12 Nov 2014 09:38:32 +0100 [thread overview]
Message-ID: <54631C88.20800@denx.de> (raw)
In-Reply-To: <CACUGKYN+RUPNL2a9knjnT3TodjVH9SjhSXzr0p9KZq2G24WgbA@mail.gmail.com>
Hi John,
On 12/11/2014 01:15, John Tobias wrote:
> Hi Otavio,
>
> In iMX6DQ data sheet the stack address is 0x0093FFB8 (page 383).
> While, in iMX6SDL datasheet (page 393) is 0x0091FFB8.
>
????
I admit that I should take a coffe, and after that maybe I can realize
what you are saying. Anyway, it is normal for processors to set the
stack pointer. If at a certain point the stack pointer is automatically
set, well, this is another case. The internal ROM will set the stack
pointer to a well defined address when it starts, but it does not mean
that is fixed for other part of code. The problem arises if from our
code (SPL) we call functions inside the ROM, and of course this can have
conflicts if they share the same address range. This is also not your
case - if that happens, two separate stack area must be taken.
What you are referring is the stack pointer of the ROM. Well, the
processors have different ROMs (only Freescale knows the differences)
and of course they can use differently the IRAM. But when the ROM gives
the control to the loaded image (SPL), this can use the whole IRAM (with
the use case exception I mentioned before).
That is the reason because ventana and Compulab have no problems at all.
IMHO what you are saying is not correct. Maybe I see things different
after a cup of coffee :-D.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2014-11-12 8:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 22:50 [U-Boot] [PATCH v4 0/7] iMX6 SabreSD SPL Support John Tobias
2014-11-11 22:50 ` [U-Boot] [PATCH v4 1/7] imx6: add spl config for mx6sabresd John Tobias
2014-11-11 22:50 ` [U-Boot] [PATCH v4 2/7] kconfig: imx6: add SUPPORT_SPL John Tobias
2014-11-11 22:50 ` [U-Boot] [PATCH v4 3/7] mmc: imx6: call spl_board_mmc_init John Tobias
2014-11-11 22:50 ` [U-Boot] [PATCH v4 4/7] imx6: add spl in the header file John Tobias
2014-11-11 22:50 ` [U-Boot] [PATCH v4 5/7] imx6: add some flexibility for defining macros John Tobias
2014-11-11 23:58 ` Otavio Salvador
2014-11-12 0:15 ` John Tobias
2014-11-12 0:52 ` Otavio Salvador
2014-11-12 0:59 ` John Tobias
2014-11-12 0:59 ` Troy Kisky
2014-11-12 1:02 ` Fabio Estevam
2014-11-12 1:10 ` John Tobias
2014-11-12 8:38 ` Stefano Babic [this message]
2014-11-12 15:56 ` Bill Pringlemeir
2014-11-11 22:50 ` [U-Boot] [PATCH v4 6/7] imx6: SPL support for iMX6 SabreSD John Tobias
2014-11-11 22:50 ` [U-Boot] [PATCH v4 7/7] imx6: add data configuration file for SPL John Tobias
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=54631C88.20800@denx.de \
--to=sbabic@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox