From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/1] sunxi: CONFIG_INIT_SP_RELATIVE=y for Pine64 LTS
Date: Tue, 2 Jun 2020 11:51:44 -0400 [thread overview]
Message-ID: <20200602155144.GL21630@bill-the-cat> (raw)
In-Reply-To: <20200531104300.31241-1-xypron.glpk@gmx.de>
On Sun, May 31, 2020 at 10:43:00AM +0000, Heinrich Schuchardt wrote:
> Booting pine64-lts_defconfig with either of CONFIG_RSA=y or CONFIG_LOG=y
> fails if CONFIG_INIT_SP_RELATIVE is not set.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> configs/pine64-lts_defconfig | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/configs/pine64-lts_defconfig b/configs/pine64-lts_defconfig
> index ef108a1a31..b03bef01b1 100644
> --- a/configs/pine64-lts_defconfig
> +++ b/configs/pine64-lts_defconfig
> @@ -1,5 +1,8 @@
> CONFIG_ARM=y
> +CONFIG_INIT_SP_RELATIVE=y
> CONFIG_ARCH_SUNXI=y
> +CONFIG_SYS_MALLOC_F_LEN=0x8000
> +CONFIG_SPL_SYS_MALLOC_F_LEN=0x400
> CONFIG_SPL=y
> CONFIG_MACH_SUN50I=y
> CONFIG_SUNXI_DRAM_LPDDR3_STOCK=y
Look at the option however. This is something that all sunxi should be
selecting. And if this is intentional as part of the design, an audit
of the other ARM64 SoCs would be in order to see who else didn't know
they needed to select this. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200602/1fe74f65/attachment.sig>
next prev parent reply other threads:[~2020-06-02 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 10:43 [PATCH 1/1] sunxi: CONFIG_INIT_SP_RELATIVE=y for Pine64 LTS Heinrich Schuchardt
2020-05-31 15:32 ` Fwd: " Heinrich Schuchardt
2020-06-02 15:51 ` Tom Rini [this message]
2020-06-02 19:45 ` Heinrich Schuchardt
2020-06-02 19:55 ` Tom Rini
2020-06-02 23:46 ` André Przywara
2020-06-03 15:47 ` Heinrich Schuchardt
2020-06-03 16:31 ` André Przywara
2020-06-03 17:07 ` Heinrich Schuchardt
2020-06-06 9:57 ` Heinrich Schuchardt
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=20200602155144.GL21630@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