From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC 0/1] Add TEE loading support to FIT image
Date: Mon, 14 Nov 2016 13:49:24 -0600 [thread overview]
Message-ID: <20161114194925.17117-1-afd@ti.com> (raw)
Hello all,
Internally[0] we use the a hook in the FIT loadable section to install
our trusted execution environment solution (OPTEE) which is packaged
in the FIT image with the rest of the platform's images. I would like
to get some feedback if this will be an acceptable solution?
This patch is the first step where we allow a platform to add a
custom hook for the "tee" type loadable. The rest of the work
is in the platform specific call and so not relevant to this RFC.
The resulting FIT .its looks something like this:
...
am57xx-evm.optee {
description = "OPTEE OS Image";
data = /incbin/("am57xx-evm.optee");
type = "tee";
arch = "arm";
compression = "none";
};
...
configurations {
am57xx-evm {
description = "Linux kernel, FDT blob, and OPTEE OS for the AM57xx EVM";
kernel = "kernel at 1";
fdt = "am57xx-evm.dtb";
loadables = "am57xx-evm.optee";
};
...
Thanks,
Andrew
[0] git://git.ti.com/ti-u-boot/ti-u-boot.git
Andrew F. Davis (1):
image: Add TEE loading to FIT loadable processing
Kconfig | 10 ++++++++++
common/image.c | 18 ++++++++++++++++++
include/image.h | 15 +++++++++++++++
3 files changed, 43 insertions(+)
--
2.10.1
next reply other threads:[~2016-11-14 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 19:49 Andrew F. Davis [this message]
2016-11-14 19:49 ` [U-Boot] [RFC 1/1] image: Add TEE loading to FIT loadable processing Andrew F. Davis
2016-11-14 20:44 ` Simon Glass
2016-11-14 21:55 ` Andrew F. Davis
2016-11-15 0:34 ` Simon Glass
2016-11-15 17:07 ` Andrew F. Davis
2016-11-16 0:18 ` Simon Glass
2016-11-15 7:55 ` Michal Simek
2016-11-15 16:43 ` Andrew F. Davis
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=20161114194925.17117-1-afd@ti.com \
--to=afd@ti.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