From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, RFC] ARM: create .secure_stack section only for PSCI
Date: Fri, 14 Oct 2016 20:13:24 -0400 [thread overview]
Message-ID: <20161015001324.GD18591@bill-the-cat> (raw)
In-Reply-To: <1474867290-17726-1-git-send-email-yamada.masahiro@socionext.com>
On Mon, Sep 26, 2016 at 02:21:30PM +0900, Masahiro Yamada wrote:
> Jon Master reports that QEMU refuses to load a U-Boot image built
> with CONFIG_ARMV7_NONSEC, but without CONFIG_ARMV7_PSCI since
> commit 5a3aae68c74e ("ARM: armv7: guard memory reserve for PSCI
> with #ifdef CONFIG_ARMV7_PSCI").
>
> It looks like only PSCI that needs the Secure stack, so move
> the #ifdef to guard the whole of .secure_stack allocation in order
> not to create the empty section.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> Reported-by: Jon Masters <jcm@redhat.com>
> Link: http://patchwork.ozlabs.org/patch/664025/
Applied to u-boot/master, thanks!
... and no, I don't know how / why this caused build failures before,
but it did and I replicated it at the time too. But I just got a
clean build everywhere. And I've added vexpress-a15 and vexpress-a9 via
QEMU to my test setup now.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161014/4691463b/attachment.sig>
prev parent reply other threads:[~2016-10-15 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 5:21 [U-Boot] [RFC PATCH] ARM: create .secure_stack section only for PSCI Masahiro Yamada
2016-09-26 15:40 ` Chen-Yu Tsai
2016-10-07 13:43 ` [U-Boot] [U-Boot, RFC] " Tom Rini
2016-10-15 0:13 ` Tom Rini [this message]
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=20161015001324.GD18591@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