From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 1/6] meta-isar: u-boot-starfive-visionfive2: Fix fetching, update to BSP version VF2_v3.0.4
Date: Sun, 4 Jun 2023 18:21:04 +0200 [thread overview]
Message-ID: <49d4662345f1b062ec267f6b796fde7fb57b4137.1685895669.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1685895669.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
JH7110_VisionFive2_devel is apparently rebasing, and now it left
our previously chosen commit orphaned behind. Update to latest BSP
U-Boot release and avoid that we may be surprised again.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
....5.bb => u-boot-starfive-visionfive2_2021.10+VF2-3.0.4.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-isar/recipes-bsp/u-boot/{u-boot-starfive-visionfive2_2022.01-rc4+VF2-2.11.5.bb => u-boot-starfive-visionfive2_2021.10+VF2-3.0.4.bb} (85%)
diff --git a/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2022.01-rc4+VF2-2.11.5.bb b/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2021.10+VF2-3.0.4.bb
similarity index 85%
rename from meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2022.01-rc4+VF2-2.11.5.bb
rename to meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2021.10+VF2-3.0.4.bb
index 0eeedc1a..1be1080e 100644
--- a/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2022.01-rc4+VF2-2.11.5.bb
+++ b/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2021.10+VF2-3.0.4.bb
@@ -5,8 +5,8 @@
require recipes-bsp/u-boot/u-boot-custom.inc
-SRC_URI += "git://github.com/starfive-tech/u-boot.git;branch=JH7110_VisionFive2_devel;protocol=https;destsuffix=u-boot-${PV}"
-SRCREV = "ac0ac696256abf412826d74ee918dd417e207d7b"
+SRC_URI += "git://github.com/starfive-tech/u-boot.git;nobranch=1;protocol=https;destsuffix=u-boot-${PV}"
+SRCREV = "b6e2b0e85c774a18ae668223a6e5f7d335895243"
DEBIAN_BUILD_DEPENDS .= ", libssl-dev:${DISTRO_ARCH}"
# when cross compiling, we need the library on the host as well, as the signature computation is done locally
--
2.35.3
next prev parent reply other threads:[~2023-06-04 16:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 16:21 [PATCH 0/6] Starfive VisionFive 2 updates Jan Kiszka
2023-06-04 16:21 ` Jan Kiszka [this message]
2023-06-12 7:50 ` [PATCH 1/6] meta-isar: u-boot-starfive-visionfive2: Fix fetching, update to BSP version VF2_v3.0.4 Jan Kiszka
2023-07-04 10:02 ` Anton Mikanovich
2023-07-04 10:36 ` Jan Kiszka
2023-07-12 7:41 ` Anton Mikanovich
2023-07-12 10:34 ` Jan Kiszka
2023-09-18 8:13 ` Jan Kiszka
2023-09-22 4:38 ` Uladzimir Bely
2023-06-04 16:21 ` [PATCH 2/6] meta-isar: starfive-visionfive2: Drop IMAGE_INSTALL from machine config Jan Kiszka
2023-06-04 16:21 ` [PATCH 3/6] meta-isar: starfive-visionfive2: Use kernel DTB Jan Kiszka
2023-06-04 16:21 ` [PATCH 4/6] meta-isar: jh7110-u-boot-spl-tool: Rework Jan Kiszka
2023-06-04 16:21 ` [PATCH 5/6] meta-isar: starfive-visionfive2: Switch to upstream U-Boot Jan Kiszka
2023-06-04 16:21 ` [PATCH 6/6] meta-isar: starfive-visionfive2: Drop obsolete recipes Jan Kiszka
2023-06-04 18:57 ` [PATCH 0/6] Starfive VisionFive 2 updates Jan Kiszka
2023-06-08 2:57 ` MOESSBAUER, Felix
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=49d4662345f1b062ec267f6b796fde7fb57b4137.1685895669.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=felix.moessbauer@siemens.com \
--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