public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Aliaksei Karpovich <akarpovich@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] u-boot: Migrate to git mirror
Date: Tue, 10 Nov 2026 17:26:50 +0100	[thread overview]
Message-ID: <f51cedb4-a573-4559-ae70-7f53972b43d9@siemens.com> (raw)
In-Reply-To: <20261110161532.1940455-1-akarpovich@ilbers.de>

On 10.11.26 17:15, Aliaksei Karpovich wrote:
> The ftp.denx.de mirror is no more accessable, so move to git releases usage.

Missing signed-off.

> ---
>  meta-isar/recipes-bsp/u-boot/u-boot-2020.10.inc                | 2 +-
>  meta-isar/recipes-bsp/u-boot/u-boot-beagleplay_2025.10.bb      | 2 +-
>  .../recipes-bsp/u-boot/u-boot-starfive-visionfive2_2024.01.bb  | 3 ++-
>  3 files changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/meta-isar/recipes-bsp/u-boot/u-boot-2020.10.inc b/meta-isar/recipes-bsp/u-boot/u-boot-2020.10.inc
> index 8ae1b8d0..be303bac 100644
> --- a/meta-isar/recipes-bsp/u-boot/u-boot-2020.10.inc
> +++ b/meta-isar/recipes-bsp/u-boot/u-boot-2020.10.inc
> @@ -6,7 +6,7 @@
>  inherit u-boot
>  
>  SRC_URI += " \
> -    https://ftp.denx.de/pub/u-boot/u-boot-${PV}.tar.bz2 \
> +    https://git.u-boot-project.org/u-boot/u-boot/-/releases/v${PV}/downloads/u-boot-${PV}.tar.bz2 \
>      "
>  SRC_URI[sha256sum] = "0d481bbdc05c0ee74908ec2f56a6daa53166cc6a78a0e4fac2ac5d025770a622"
>  
> diff --git a/meta-isar/recipes-bsp/u-boot/u-boot-beagleplay_2025.10.bb b/meta-isar/recipes-bsp/u-boot/u-boot-beagleplay_2025.10.bb
> index a40d4e04..dcf0e8a0 100644
> --- a/meta-isar/recipes-bsp/u-boot/u-boot-beagleplay_2025.10.bb
> +++ b/meta-isar/recipes-bsp/u-boot/u-boot-beagleplay_2025.10.bb
> @@ -12,7 +12,7 @@ MAINTAINER = "isar-users <isar-users@googlegroups.com>"
>  TI_FIRMWARE_SRCREV = "0a37dc07b1120127eba73c7196a0b532350b9639"
>  
>  SRC_URI += " \
> -    https://ftp.denx.de/pub/u-boot/u-boot-${PV}.tar.bz2 \
> +    https://git.u-boot-project.org/u-boot/u-boot/-/releases/v${PV}/downloads/u-boot-${PV}.tar.bz2 \
>      https://github.com/TexasInstruments/ti-linux-firmware/raw/${TI_FIRMWARE_SRCREV}/ti-sysfw/ti-fs-firmware-am62x-gp.bin;downloadfilename=ti-fs-firmware-am62x-gp.bin;name=sysfw \
>      https://github.com/TexasInstruments/ti-linux-firmware/raw/${TI_FIRMWARE_SRCREV}/ti-sysfw/ti-fs-stub-firmware-am62x-gp.bin;downloadfilename=ti-fs-stub-firmware-am62x-gp.bin;name=sysfw-stub \
>      https://github.com/TexasInstruments/ti-linux-firmware/raw/${TI_FIRMWARE_SRCREV}/ti-dm/am62xx/ipc_echo_testb_mcu1_0_release_strip.xer5f;downloadfilename=ipc_echo_testb_mcu1_0_release_strip.xer5f;name=dm \
> diff --git a/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2024.01.bb b/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2024.01.bb
> index 7abba742..a40fbf54 100644
> --- a/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2024.01.bb
> +++ b/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2024.01.bb
> @@ -9,7 +9,8 @@ MAINTAINER = "isar-users <isar-users@googlegroups.com>"
>  
>  COMPATIBLE_MACHINE = "^(starfive-visionfive2)$"
>  
> -SRC_URI += "https://ftp.denx.de/pub/u-boot/u-boot-${PV}.tar.bz2 \
> +SRC_URI += " \
> +    https://git.u-boot-project.org/u-boot/u-boot/-/releases/v${PV}/downloads/u-boot-${PV}.tar.bz2 \
>      file://0001-scripts-dtc-pylibfdt-libfdt.i_shipped-Use-SWIG_Appen.patch \
>      file://starfive-visionfive2-rules.tmpl"
>  SRC_URI[sha256sum] = "b99611f1ed237bf3541bdc8434b68c96a6e05967061f992443cb30aabebef5b3"

Ah, using the release artifacts is actually better than the generated
archives [1] - less load on the server, likely faster access.

Jan

[1]
https://gitlab.com/cip-project/cip-core/isar-cip-core/-/commit/ab5c16004580286d1a0d1aeabf1029a62a113019

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/f51cedb4-a573-4559-ae70-7f53972b43d9%40siemens.com.

      reply	other threads:[~2026-11-10 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 16:15 Aliaksei Karpovich
2026-11-10 16:26 ` 'Jan Kiszka' via isar-users [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=f51cedb4-a573-4559-ae70-7f53972b43d9@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=akarpovich@ilbers.de \
    --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