From: Troy Kisky <troy.kisky@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 5/7] imx6: add some flexibility for defining macros
Date: Tue, 11 Nov 2014 17:59:57 -0700 [thread overview]
Message-ID: <5462B10D.10807@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKpeZB29incinOQ1_ZfiB2gASj3f5QnCGpRjbgXyTtzO_A@mail.gmail.com>
On 11/11/2014 5:52 PM, Otavio Salvador wrote:
> On Tue, Nov 11, 2014 at 10:15 PM, John Tobias <john.tobias.ph@gmail.com> wrote:
>> In iMX6DQ data sheet the stack address is 0x0093FFB8 (page 383).
>> While, in iMX6SDL datasheet (page 393) is 0x0091FFB8.
>
> I am worrying how Compulab and Gateworks are using SPL if it is wrong.
>
iMX6SDL has 128KB OCRAM, 0x00900000 - 0x0091ffff
iMX6DQ has 256KB OCRAM, 0x00900000 - 0x0093ffff
So, if we want 1 image to support both, we should choose 0x0091FFB8.
I don't know whether that is a goal here.
next prev parent reply other threads:[~2014-11-12 0:59 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 [this message]
2014-11-12 1:02 ` Fabio Estevam
2014-11-12 1:10 ` John Tobias
2014-11-12 8:38 ` Stefano Babic
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=5462B10D.10807@boundarydevices.com \
--to=troy.kisky@boundarydevices.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.