From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2] trusted-firmware-a: Switch SRC_URI from git to tarballs
Date: Mon, 01 Jul 2024 06:13:40 +0300 [thread overview]
Message-ID: <69072bfd277512ec0f0ec25e88d091f3cb4ad8a5.camel@ilbers.de> (raw)
In-Reply-To: <20240628032505.7184-1-ubely@ilbers.de>
On Fri, 2024-06-28 at 06:24 +0300, 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-beagleplay_2.10.bb | 6 +++-
> --
> .../trusted-firmware-a/trusted-firmware-a-stm32mp15x_2.4.bb | 6 +++-
> --
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> Changes since v1:
> - Added sha256sum for downloaded tarballs
>
> 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..d7f82032 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,10 @@
>
> 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"
> +SRC_URI[sha256sum] =
> "2e18b881ada9198173238cca80086c787b1fa3f698944bde1743142823fc511c"
>
> -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..b36dc3ee 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,10 @@
>
> 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"
> +SRC_URI[sha256sum] =
> "4bfda9fdbe5022f2e88ad3344165f7d38a8ae4a0e2d91d44d9a1603425cc642d"
>
> -S = "${WORKDIR}/git"
> +S = "${WORKDIR}/arm-trusted-firmware-${PV}"
>
> DEBIAN_BUILD_DEPENDS += ", device-tree-compiler"
>
> --
> 2.44.2
>
Applied to next.
--
Best regards,
Uladzimir.
prev parent reply other threads:[~2024-07-01 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 3:24 Uladzimir Bely
2024-07-01 3:13 ` Uladzimir Bely [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=69072bfd277512ec0f0ec25e88d091f3cb4ad8a5.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.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