From: Tom Rini <trini@konsulko.com>
To: Raymond Mao <raymond.mao@linaro.org>
Cc: u-boot@lists.denx.de,
Jerome Forissier <jerome.forissier@linaro.org>,
Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi>,
Simon Glass <sjg@chromium.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Michal Simek <michal.simek@amd.com>,
Adriano Cordova <adrianox@gmail.com>,
Patrick Rudolph <patrick.rudolph@9elements.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [PATCH v5 1/5] docker: add OP-TEE and TF-A build for testing Firmware Handoff
Date: Tue, 21 Oct 2025 09:37:48 -0600 [thread overview]
Message-ID: <20251021153748.GD6688@bill-the-cat> (raw)
In-Reply-To: <20251021153443.219326-2-raymond.mao@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]
On Tue, Oct 21, 2025 at 08:34:33AM -0700, Raymond Mao wrote:
> Fetch OP-TEE (4.7.0), TF-A (v2.13.0), MbedTLS (v3.6) and build
> bl1 and fip with both Firmware Handoff and Measured Boot enabled.
>
> Signed-off-by: Raymond Mao <raymond.mao@linaro.org>
> Acked-by: Jerome Forissier <jerome.forissier@linaro.org>
> ---
> Changes in V2:
> - Move OP-TEE dependencies into the common group.
> - Fetch MbedTLS/TF-A and build bl1/fip in dockerfile instead of
> post-buildman script.
> - Remove Trust Boot related build options.
> Changes in V3:
> - Clean-up of OP-TEE deps.
> Changes in V4:
> - Minimize OP-TEE build options.
> Changes in V5:
> - Add '--depth=1' and '--branch' when cloning OP-TEE, MbedTLS and TF-A.
>
> tools/docker/Dockerfile | 38 +++++++++++++++++++++++++++++++++++---
> 1 file changed, 35 insertions(+), 3 deletions(-)
>
> diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile
> index 5b4c75f8400..3286b2ba6b2 100644
> --- a/tools/docker/Dockerfile
> +++ b/tools/docker/Dockerfile
[snip]
> @@ -227,10 +229,22 @@ RUN git clone https://gitlab.com/qemu-project/qemu.git /tmp/qemu && \
> make -j$(nproc) all install && \
> rm -rf /tmp/qemu
>
> -# Build fiptool
> -RUN git clone https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git /tmp/tf-a && \
> +# Build OP-TEE for qemu_arm64
> +RUN git clone --depth=1 --branch 4.7.0 https://github.com/OP-TEE/optee_os.git /tmp/optee_os && \
I was asking for this to be two lines:
RUN git clone --depth=1 https://github.com/OP-TEE/optee_os.git /tmp/optee_os \
--branch 4.7.0 && \
So that updates to later versions can be a single line change that's
also clearly just changing the version number.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-21 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 15:34 [PATCH v5 0/5] Enable Firmware Handoff CI test on qemu_arm64 Raymond Mao
2025-10-21 15:34 ` [PATCH v5 1/5] docker: add OP-TEE and TF-A build for testing Firmware Handoff Raymond Mao
2025-10-21 15:37 ` Tom Rini [this message]
2025-10-21 15:34 ` [PATCH v5 2/5] pytest: add test script to validate " Raymond Mao
2025-10-21 15:34 ` [PATCH v5 3/5] configs: select CMD_BLOBLIST for Firmware Handoff testing Raymond Mao
2025-10-21 15:34 ` [PATCH v5 4/5] ci: check existence of bl1 and fip in the test script Raymond Mao
2025-10-21 15:34 ` [PATCH v5 5/5] ci: add test entries for qemu_arm64_tfa_fw_handoff Raymond Mao
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=20251021153748.GD6688@bill-the-cat \
--to=trini@konsulko.com \
--cc=adrianox@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=michal.simek@amd.com \
--cc=patrick.rudolph@9elements.com \
--cc=raymond.mao@linaro.org \
--cc=sjg@chromium.org \
--cc=tuomas.tynkkynen@iki.fi \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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