From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 04/11] linux-mainline: Add fTPM support
Date: Tue, 25 Jul 2023 16:43:52 +0300 [thread overview]
Message-ID: <b07fed638fd1901c37c1cfc99cceff47b29289f8.camel@ilbers.de> (raw)
In-Reply-To: <241b689507a6e8933d2d92046f5cbda6d125b3ec.1689872892.git.jan.kiszka@siemens.com>
On Thu, 2023-07-20 at 19:08 +0200, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Needed for the stm32mp15x demo of fTPM.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> meta-isar/recipes-kernel/linux/files/ftpm-module.cfg | 3 +++
> meta-isar/recipes-kernel/linux/linux-mainline_5.4.203.bb | 2 ++
> 2 files changed, 5 insertions(+)
> create mode 100644 meta-isar/recipes-kernel/linux/files/ftpm-
> module.cfg
>
> diff --git a/meta-isar/recipes-kernel/linux/files/ftpm-module.cfg
> b/meta-isar/recipes-kernel/linux/files/ftpm-module.cfg
> new file mode 100644
> index 00000000..f47620bc
> --- /dev/null
> +++ b/meta-isar/recipes-kernel/linux/files/ftpm-module.cfg
> @@ -0,0 +1,3 @@
> +CONFIG_TEE=m
> +CONFIG_OPTEE=m
> +CONFIG_TCG_FTPM_TEE=m
> diff --git a/meta-isar/recipes-kernel/linux/linux-mainline_5.4.203.bb
> b/meta-isar/recipes-kernel/linux/linux-mainline_5.4.203.bb
> index 76f73f02..27ebf131 100644
> --- a/meta-isar/recipes-kernel/linux/linux-mainline_5.4.203.bb
> +++ b/meta-isar/recipes-kernel/linux/linux-mainline_5.4.203.bb
> @@ -14,6 +14,8 @@ SRC_URI += " \
> file://x86_64_defconfig \
> file://no-ubifs-fs.cfg \
> file://no-root-nfs.cfg;apply=no"
> +SRC_URI:append:stm32mp15x = " \
> + file://ftpm-module.cfg"
>
> SRC_URI[sha256sum] =
> "fc933f5b13066cfa54aacb5e86747a167bad1d8d23972e4a03ab5ee36c29798a"
>
> --
> 2.35.3
>
This patch seems to make CI fail at "CrossTest.test_cross" build.
In this test we build in parallel two "armhf" targets that both use
"mainline" kernel - stm32mp15x-bullseye and de0-nano-soc-bullseye.
Due to the same distro/kernel/arch they are both build in parallel in
the same workdir (build/tmp/work/debian-bullseye-armhf/linux-
mainline/5.4.203-r0) but due to "append:stm32mp15x" they should use
different kernel config. This causes two parallel confliction builds
and results in some weird error:
```
cat: /workspace/build/isar_ub_devel_fast/469/build/tmp/work/debian-
bullseye-armhf/linux-mainline/5.4.203-r0/rootfs/dpkg_partial.log: No
such file or directory
```
By the way, NoCrossTest.test_nocross doesn't fail since it doesn't
build another bullseye/armhf linux-mainline in parallel with one for
stm32mp15x.
next prev parent reply other threads:[~2023-07-25 13:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 17:08 [PATCH v3 00/11] Fixes, cleanups and updates for OP-TEE and TAs Jan Kiszka
2023-07-20 17:08 ` [PATCH v3 01/11] optee-client: Add missing runtime dependency Jan Kiszka
2023-07-20 17:08 ` [PATCH v3 02/11] optee-client: Unbind ftpm, rather than remove its driver Jan Kiszka
2023-07-20 17:08 ` [PATCH v3 03/11] optee-examples-stm32mp15x: Fix parsing error for non-stm32mp15x machines Jan Kiszka
2023-07-20 17:08 ` [PATCH v3 04/11] linux-mainline: Add fTPM support Jan Kiszka
2023-07-25 13:43 ` Uladzimir Bely [this message]
2023-07-26 8:31 ` Uladzimir Bely
2023-07-26 9:32 ` Jan Kiszka
2023-07-27 7:07 ` Uladzimir Bely
2023-07-20 17:08 ` [PATCH v3 05/11] initramfs-tee-{ftpm,supplicant}-hook: Move sync loop to ftpm-hook Jan Kiszka
2023-07-20 17:08 ` [PATCH v3 06/11] initramfs-tee-supplicant-hook: Account for modular optee Jan Kiszka
2023-07-20 17:08 ` [PATCH v3 07/11] initramfs-tee-ftpm-hook: Lift timeout to 30 s Jan Kiszka
2023-07-20 17:08 ` [PATCH v3 08/11] Drop stm32mp15x-initramfs in favor of image enabling Jan Kiszka
2023-07-20 17:08 ` [PATCH v3 09/11] optee-ftpm-stm32mp15x: Recipe cleanups Jan Kiszka
2023-07-20 17:08 ` [PATCH v3 10/11] optee-ftpm-stm32mp15x: Update WolfSSL to 5.6.3 Jan Kiszka
2023-07-20 17:08 ` [PATCH v3 11/11] optee-ftpm-stm32mp15x: Add patch to fix parallel build issues Jan Kiszka
2023-07-27 7:13 ` Uladzimir Bely
2023-07-28 8:58 ` Uladzimir Bely
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=b07fed638fd1901c37c1cfc99cceff47b29289f8.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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