From: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] Odroid XU3 - exynos5422 - SPL - iRAM/sRAM address
Date: Wed, 21 Jan 2015 10:54:31 +0100 [thread overview]
Message-ID: <1421834071.6818.79.camel@collabora.co.uk> (raw)
In-Reply-To: <CANoR_OA9pnPNeY5YLdXs6UuarHtymwTbe=5HDETJz24SXHyBzg@mail.gmail.com>
On Tue, 2015-01-20 at 15:29 -0800, Suriyan Ramasami wrote:
> Hello Kevin,
>
> On Tue, Jan 20, 2015 at 2:43 PM, Kevin Hilman <khilman@kernel.org> wrote:
> > Suriyan Ramasami <suriyan.r@gmail.com> writes:
> I am currently working only on the XU3 (I thought there was no
> interest, so I let it slide). I probably should say that the Exynos
> secure firmware support needs to be tweaked in U-Boot. Maybe other
> SoCs are supported? I am not sure.
Thanks for the update!
> > Also, I'm still a bit unsure where the switch from secure to NS world
> > happens. Is that in BL1? or somewhere in BL2? If it's in BL2, have you
> > tried switching secure mode off?
> >
>
> I know for sure that the signed BL2 does switch from Hyp to NS. This
> BL2 that I am referring to is HK's nomenclature, which translates to
> BL1 (SPL) in UBoot lingo. Hence, this adds some confusion in the
> discussions!
It does!. What i was wondering if there would be potential to get a
signed BL2 which does *not* do the switch to the NS world, such that an
unsigned chain-loaded SPL could (optionally) do that.
> The blobs are as follows: (possibly listed in the HK web pages)
> BL0 (signed encrypted blob from Samsung).
> This loads HK's signed BL2 (this is U-Boot SPL)
> This loads U-Boot (U-Boot BL2) and the Trustzone
>
> Also, no matter what mode the odroid xu3 is in, the linux kernel from
> what I can tell depending on the secure-firmware dts entry (which is
> present) will use the NS + 1c area when powering on the CPU. Hence,
> its mandatory to have code there.
Well this is something we can tune as required in case it would be
possible to start linux in both secure and NS mode.
--
Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Collabora Ltd.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6170 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150121/e0bcbc0d/attachment.bin>
next prev parent reply other threads:[~2015-01-21 9:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANoR_OBusZCF1cRFhrTem1hh86pJpGOFU-u2Jw+MGfAHi1sxXQ@mail.gmail.com>
[not found] ` <CANoR_OCPauSqFZqos48wBPXjBSu1triHC1ftXko6Rs3y-jaWVg@mail.gmail.com>
[not found] ` <1421746560.6818.37.camel@collabora.co.uk>
2015-01-20 16:40 ` [U-Boot] Odroid XU3 - exynos5422 - SPL - iRAM/sRAM address Sjoerd Simons
2015-01-20 19:37 ` Suriyan Ramasami
2015-01-20 21:30 ` Kevin Hilman
2015-01-20 22:06 ` Suriyan Ramasami
2015-01-20 22:43 ` Kevin Hilman
2015-01-20 23:29 ` Suriyan Ramasami
2015-01-20 23:38 ` Suriyan Ramasami
2015-01-21 0:19 ` Suriyan Ramasami
2015-01-21 19:01 ` Kevin Hilman
2015-01-21 9:54 ` Sjoerd Simons [this message]
2015-01-22 0:54 ` Kevin Hilman
2015-01-22 5:54 ` Suriyan Ramasami
2015-01-22 17:51 ` Kevin Hilman
2015-01-23 1:46 ` Suriyan Ramasami
2015-01-28 7:17 ` Joonyoung Shim
2015-02-25 21:38 ` Kevin Hilman
2015-02-25 23:00 ` Suriyan Ramasami
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=1421834071.6818.79.camel@collabora.co.uk \
--to=sjoerd.simons@collabora.co.uk \
--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