From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] boot/optee-os: OP-TEE secure world
Date: Thu, 22 Nov 2018 22:18:35 +0200 [thread overview]
Message-ID: <87tvk8euhw.fsf@tkos.co.il> (raw)
In-Reply-To: <1542900177-17343-1-git-send-email-etienne.carriere@linaro.org>
Hi Etienne,
Thanks for your contribution. I have a few comments below.
Etienne Carriere writes:
> OP-TEE OS is maintained by the OP-TEE project. It provides an
> open source solution for development and integration of secure
> services for Armv7-A and Armv8-A CPU based platforms supporting
> the TrustZone technology. This technology enables CPUs to
> concurrently host a secure world as the OP-TEE OS and a non-secure
> world as a Linux based OS.
>
> The OP-TEE project maintains other packages to leverage OP-TEE on
> Linux kernel based OSes. An OP-TEE interface driver is available
> in the Linux kernel since 4.12 upon CONFIG_OPTEE.
>
> https://www.op-tee.org/
> https://github.com/OP-TEE/optee_os
>
> Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
...
> diff --git a/boot/optee-os/Config.in b/boot/optee-os/Config.in
> new file mode 100644
> index 0000000..5968531
> --- /dev/null
> +++ b/boot/optee-os/Config.in
> @@ -0,0 +1,102 @@
> +config BR2_TARGET_OPTEE_OS
> + bool "optee_os"
> + depends on BR2_aarch64 || BR2_arm
> + select BR2_PACKAGE_OPENSSL # host tool
Which host? Is that the host below which OPTEE OS runs? This is usually
called target in the Buildroot lingo. Please clarify in a comment.
Is that a build time dependency? If so you need to add openssl to
_DEPENDENCIES.
> + help
> + OP-TEE OS provides the secure world boot image and the trust
> + application development kit of the OP-TEE project. OP-TEE OS
> + also provides generic trusted application one can embedded
> + into its system.
> +
> + http://github.org/OP-TEE/optee_os
> +
> +if BR2_TARGET_OPTEE_OS
> +
> +choice
> + prompt "OP-TEE OS version"
> + default BR2_TARGET_OPTEE_OS_LATEST
> + help
> + Select the version of OP-TEE OS you want to use
Is there a practical need to support selection separate version
selection for each OPTEE component? If not then I think this version
selection should apply to all other components.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2018-11-22 20:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 15:22 [Buildroot] [PATCH 1/5] boot/optee-os: OP-TEE secure world Etienne Carriere
2018-11-22 15:22 ` [Buildroot] [PATCH 2/5] optee-client: new package Etienne Carriere
2018-11-23 11:48 ` Shyam Saini
2018-11-23 18:10 ` [Buildroot] [PATCH v2 " Etienne Carriere
2018-11-22 15:22 ` [Buildroot] [PATCH 3/5] optee-benchmark: " Etienne Carriere
2018-11-23 18:10 ` [Buildroot] [PATCH v2 " Etienne Carriere
2018-11-22 15:22 ` [Buildroot] [PATCH 4/5] optee-examples: " Etienne Carriere
2018-11-23 11:48 ` Shyam Saini
2018-11-23 18:11 ` [Buildroot] [PATCH v2 " Etienne Carriere
2018-11-22 15:22 ` [Buildroot] [PATCH 5/5] optee-test: " Etienne Carriere
2018-11-23 3:06 ` Carlos Santos
2018-11-23 10:10 ` Etienne Carriere
2018-11-23 11:49 ` Shyam Saini
2018-11-23 18:11 ` [Buildroot] [PATCH v2 " Etienne Carriere
2018-11-22 20:18 ` Baruch Siach [this message]
2018-11-23 8:21 ` [Buildroot] [PATCH 1/5] boot/optee-os: OP-TEE secure world Etienne Carriere
2018-11-23 10:05 ` Baruch Siach
2018-11-23 10:13 ` Etienne Carriere
2018-11-23 3:01 ` Carlos Santos
2018-11-23 7:33 ` Etienne Carriere
2018-11-23 8:35 ` Shyam Saini
2018-11-23 9:05 ` Etienne Carriere
2018-11-23 15:08 ` Etienne Carriere
2018-11-23 18:09 ` [Buildroot] [PATCH v2 1/5] boot/optee-os: new package Etienne Carriere
2019-01-07 10:24 ` [Buildroot] [PATCH v3 1/7] " Etienne Carriere
2019-01-07 10:24 ` [Buildroot] [PATCH v3 2/7] optee-client: " Etienne Carriere
2019-01-07 10:24 ` [Buildroot] [PATCH v3 3/7] optee-examples: " Etienne Carriere
2019-01-07 10:24 ` [Buildroot] [PATCH v3 4/7] optee-test: " Etienne Carriere
2019-01-07 10:24 ` [Buildroot] [PATCH v3 5/7] optee-benchmark: " Etienne Carriere
2019-01-07 10:24 ` [Buildroot] [PATCH v3 6/7] configs/qemu_armv7a_tz_virt: Armv7-A emulation with TrustZone services Etienne Carriere
2019-01-07 10:24 ` [Buildroot] [PATCH v3 7/7] configs/qemu_aarch64_tz_virt: AArch64 " Etienne Carriere
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=87tvk8euhw.fsf@tkos.co.il \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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