From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 1/2] meta-isar: opensbi-sifive-fu540: Update to 0.8
Date: Fri, 16 Oct 2020 08:42:04 +0200 [thread overview]
Message-ID: <3541f5224ab1c232402bc0e82917e543e9921a32.1602830524.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1602830524.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
This fixes a build breakage with more recent sid.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
...{opensbi-sifive-fu540_0.5.bb => opensbi-sifive-fu540_0.8.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-isar/recipes-bsp/opensbi/{opensbi-sifive-fu540_0.5.bb => opensbi-sifive-fu540_0.8.bb} (87%)
diff --git a/meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.5.bb b/meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.8.bb
similarity index 87%
rename from meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.5.bb
rename to meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.8.bb
index b9d0c3e1..6ab83483 100644
--- a/meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.5.bb
+++ b/meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.8.bb
@@ -8,7 +8,7 @@ inherit dpkg
SRC_URI = " \
https://github.com/riscv/opensbi/archive/v${PV}.tar.gz;downloadfilename=opensbi-${PV}.tar.gz \
file://sifive-fu540-rules"
-SRC_URI[sha256sum] = "bc82f1e63663cafb7976b324d8a01263510cfd816063dc89e0ccffb9763fb1dd"
+SRC_URI[sha256sum] = "17e048ac765e92e15f7436b604452614cf88dc2bcbbaab18cdc024f3fdd4c575"
S = "${WORKDIR}/opensbi-${PV}"
--
2.26.2
next prev parent reply other threads:[~2020-10-16 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 6:42 [PATCH 0/2] sifive-fu540: opensbi build fix and cleanup Jan Kiszka
2020-10-16 6:42 ` Jan Kiszka [this message]
2020-10-16 6:42 ` [PATCH 2/2] meta-isar: opensbi-sifive-fu540: Use DEBIAN_BUILD_DEPENDS Jan Kiszka
2020-11-26 15:56 ` [PATCH 0/2] sifive-fu540: opensbi build fix and cleanup Anton Mikanovich
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=3541f5224ab1c232402bc0e82917e543e9921a32.1602830524.git.jan.kiszka@siemens.com \
--to=jan.kiszka@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