From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] trusted-firmware-a: Switch SRC_URI from git to tarballs
Date: Wed, 26 Jun 2024 09:43:58 +0200 [thread overview]
Message-ID: <8ec35890-ea51-4a1a-b835-548d70a9cc47@siemens.com> (raw)
In-Reply-To: <20240626063821.9747-1-ubely@ilbers.de>
On 26.06.24 08:38, Uladzimir Bely wrote:
> Commit f7c0df35 should have helped with periodic fetch failures,
> but the issue is happens even with github.
>
> Switch to fetching tarballs that are smaller in size than
> git tree and are expected to be more stable when fetching.
>
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
> .../trusted-firmware-a/trusted-firmware-a-beagleplay_2.10.bb | 5 ++---
> .../trusted-firmware-a/trusted-firmware-a-stm32mp15x_2.4.bb | 5 ++---
> 2 files changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-beagleplay_2.10.bb b/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-beagleplay_2.10.bb
> index bf1e3f05..675a6d87 100644
> --- a/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-beagleplay_2.10.bb
> +++ b/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-beagleplay_2.10.bb
> @@ -5,10 +5,9 @@
>
> require recipes-bsp/trusted-firmware-a/trusted-firmware-a-custom.inc
>
> -SRC_URI += "git://github.com/ARM-software/arm-trusted-firmware.git;protocol=https;branch=master"
> -SRCREV = "b6c0948400594e3cc4dbb5a4ef04b815d2675808"
> +SRC_URI += "https://github.com/ARM-software/arm-trusted-firmware/archive/v${PV}.tar.gz;downloadfilename=arm-trusted-firmware-${PV}.tar.gz"
>
Seem you are missing the checksum for the tarball.
Jan
> -S = "${WORKDIR}/git"
> +S = "${WORKDIR}/arm-trusted-firmware-${PV}"
>
> TF_A_PLATFORM = "k3"
> TF_A_EXTRA_BUILDARGS = "CFG_ARM64=y TARGET_BOARD=lite SPD=opteed"
> diff --git a/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-stm32mp15x_2.4.bb b/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-stm32mp15x_2.4.bb
> index 9927b460..ca411c71 100644
> --- a/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-stm32mp15x_2.4.bb
> +++ b/meta-isar/recipes-bsp/trusted-firmware-a/trusted-firmware-a-stm32mp15x_2.4.bb
> @@ -5,10 +5,9 @@
>
> require recipes-bsp/trusted-firmware-a/trusted-firmware-a-custom.inc
>
> -SRC_URI += "git://github.com/ARM-software/arm-trusted-firmware.git;protocol=https;branch=master"
> -SRCREV = "e2c509a39c6cc4dda8734e6509cdbe6e3603cdfc"
> +SRC_URI += "https://github.com/ARM-software/arm-trusted-firmware/archive/v${PV}.tar.gz;downloadfilename=arm-trusted-firmware-${PV}.tar.gz"
>
> -S = "${WORKDIR}/git"
> +S = "${WORKDIR}/arm-trusted-firmware-${PV}"
>
> DEBIAN_BUILD_DEPENDS += ", device-tree-compiler"
>
--
Siemens AG, Technology
Linux Expert Center
prev parent reply other threads:[~2024-06-26 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 6:38 Uladzimir Bely
2024-06-26 7:43 ` Jan Kiszka [this message]
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=8ec35890-ea51-4a1a-b835-548d70a9cc47@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.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