From: Marc Zyngier <marc.zyngier@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 06/13] ARM: HYP/non-sec: allow relocation to secure RAM
Date: Thu, 19 Feb 2015 13:58:45 +0000 [thread overview]
Message-ID: <54E5EC15.5090106@arm.com> (raw)
In-Reply-To: <d3077a77-dc57-4444-9268-2c5c401c19f3@googlegroups.com>
On 18/02/15 17:42, surya.satyavolu at sirabtech.com wrote:
> I am trying to bring up xen suing u-boot that has this patch.
> Unfortunately as soon as the code tries to call _nonsec_init through
> secure_ram_addr in arm7_init_nonsec function in virt-v7.c I get an
> undefined instruction exception. I suspect the
> CONFIG_ARMV7_SECURE_BASE needs to be defined to a particular value.
> What should that be defined to for omap5432?
I'm afraid you're barking up the wrong tree.
TI, in its infinite wisdom, drops directly to *non-secure*. So, there is
nothing you can actually do (maybe there's a way to go back to secure
mode, but that's certainly not documented).
The consequence of the above is that you cannot implement PSCI on
OMAP4/5. You'll have to add you own code to promote your CPUs to HYP
(there is a secure call for this).
Good luck,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-02-19 13:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 13:36 [U-Boot] [PATCH v3 00/13] ARMv7: add PSCI support to u-boot Marc Zyngier
2014-02-15 13:36 ` [U-Boot] [PATCH v3 01/13] ARM: HYP/non-sec: move switch to non-sec to the last boot phase Marc Zyngier
2014-02-15 13:36 ` [U-Boot] [PATCH v3 02/13] ARM: HYP/non-sec: add a barrier after setting SCR.NS==1 Marc Zyngier
2014-02-15 13:36 ` [U-Boot] [PATCH v3 03/13] ARM: non-sec: reset CNTVOFF to zero Marc Zyngier
2014-02-15 13:36 ` [U-Boot] [PATCH v3 04/13] ARM: add missing HYP mode constant Marc Zyngier
2014-02-15 13:36 ` [U-Boot] [PATCH v3 05/13] ARM: HYP/non-sec: add separate section for secure code Marc Zyngier
2014-02-15 13:36 ` [U-Boot] [PATCH v3 06/13] ARM: HYP/non-sec: allow relocation to secure RAM Marc Zyngier
2014-05-30 2:25 ` [U-Boot] smp_kick_all_cpus() function's role TigerLiu at via-alliance.com
2014-05-30 8:56 ` Marc Zyngier
2014-06-03 2:16 ` TigerLiu at via-alliance.com
2014-06-03 9:19 ` Marc Zyngier
2014-06-03 9:41 ` TigerLiu at via-alliance.com
2014-06-03 9:46 ` Marc Zyngier
2015-02-18 17:42 ` [U-Boot] [PATCH v3 06/13] ARM: HYP/non-sec: allow relocation to secure RAM surya.satyavolu at sirabtech.com
2015-02-19 13:58 ` Marc Zyngier [this message]
2014-02-15 13:36 ` [U-Boot] [PATCH v3 07/13] ARM: HYP/non-sec: add generic ARMv7 PSCI code Marc Zyngier
2014-02-15 13:36 ` [U-Boot] [PATCH v3 08/13] ARM: HYP/non-sec: add the option for a second-stage monitor Marc Zyngier
2014-02-15 13:36 ` [U-Boot] [PATCH v3 09/13] ARM: convert arch_fixup_memory_node to a generic FDT fixup function Marc Zyngier
2014-02-15 13:36 ` [U-Boot] [PATCH v3 10/13] ARM: HYP/non-sec/PSCI: emit DT nodes Marc Zyngier
2014-05-07 19:24 ` Ian Campbell
2014-05-08 6:22 ` Marc Zyngier
2014-05-08 7:07 ` Ian Campbell
2014-02-15 13:36 ` [U-Boot] [PATCH v3 11/13] sunxi: fix SRAM_B/SRAM_D memory map Marc Zyngier
2014-02-15 13:36 ` [U-Boot] [PATCH v3 12/13] sunxi: HYP/non-sec: add sun7i PSCI backend Marc Zyngier
2014-02-15 13:36 ` [U-Boot] [PATCH v3 13/13] sunxi: HYP/non-sec: configure CNTFRQ on all CPUs Marc Zyngier
2014-02-15 14:45 ` [U-Boot] [PATCH v3 00/13] ARMv7: add PSCI support to u-boot Albert ARIBAUD
2014-02-16 12:01 ` Marc Zyngier
2014-04-16 14:45 ` Albert ARIBAUD
2014-04-16 16:09 ` Marc Zyngier
2014-04-16 18:15 ` Jon Loeliger
2014-04-17 8:34 ` Albert ARIBAUD
2014-04-17 8:58 ` Marc Zyngier
2014-04-17 9:41 ` Albert ARIBAUD
2014-04-17 10:33 ` Ian Campbell
2014-04-17 19:55 ` Jon Loeliger
2014-04-18 7:48 ` Marc Zyngier
[not found] ` <CAJgR-BgnbboBcVUeA2ujzwCHZ4kPyedidC42VSrE5U75Dk+CAg@mail.gmail.com>
2014-04-17 20:01 ` [U-Boot] Fwd: " Jon Loeliger
2014-04-18 8:08 ` Marc Zyngier
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=54E5EC15.5090106@arm.com \
--to=marc.zyngier@arm.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