From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Keystone 2 sram scratch address?
Date: Sun, 7 Oct 2018 09:59:12 -0400 [thread overview]
Message-ID: <20181007135912.GP15855@bill-the-cat> (raw)
Hey folks,
So as part of Simon's patch[1] to move CONFIG_SPL_TEXT_BASE to Kconfig
I've run into a problem on Keystone 2 platforms, specifically the HS
variants. What keystone does is define the SRAM scratch address
relative to the end of our regular SRAM usage for SPL. This is I think
in part due to the large variation in the SRAM size on these parts
contain and a desire to be able to more easily support the larger sizes.
This is fine on the non-HS parts where we enable and build SPL so can
play these games. But on the HS parts (or at least k2l_hs_evm
k2e_hs_evm k2hk_hs_evm k2g_hs_evm) we don't use SPL, so once moving
CONFIG_SPL_TEXT_BASE to Kconfig we don't have it defined and a few
places fall apart. Can we find some constant we could use for
CONFIG_SYS_INIT_SP_ADDR and then for the EEPROM copy we make on K2G?
Thanks!
[1]: https://patchwork.ozlabs.org/patch/976918/
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181007/652a0fa0/attachment.sig>
next reply other threads:[~2018-10-07 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 13:59 Tom Rini [this message]
2018-10-08 5:17 ` [U-Boot] Keystone 2 sram scratch address? Lokesh Vutla
2018-10-08 12:16 ` Tom Rini
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=20181007135912.GP15855@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox