From: Tim Orling <ticotimo@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] opensbi-sifive-fu540: upgrade to 0.9
Date: Sat, 18 Sep 2021 11:14:34 -0700 [thread overview]
Message-ID: <CANx9H-DfAChFP_6LvF4oEo33WPjWMUU9-gaihGhL022zaESMGQ@mail.gmail.com> (raw)
In-Reply-To: <CANx9H-DzNKByG8tu4-CGFGhAZYLZrY8bPgKAB9UyVq5aU2r40w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3339 bytes --]
On Sat, Sep 18, 2021 at 11:05 AM Tim Orling <ticotimo@gmail.com> wrote:
>
>
> On Fri, Sep 17, 2021 at 11:34 PM Jan Kiszka <jan.kiszka@web.de> wrote:
>
>> On 17.09.21 21:12, Tim Orling wrote:
>> > This release has:
>> >
>> > * Lots of fixes and improvements
>> > * Optimized trap handler for both RV32 and RV64
>> > * Domain support for system-level partitioning
>> > * Device tree based domain configuration
>> > * SBI v0.3 SRST extension
>> > * More detailed boot-time prints
>> > * Makefile option to use toolchain default ISA and ABI
>> >
>> > u-boot.bin is now in
>> > /usr/lib/u-boot/sifive_unleashed/u-boot.bin
>> >
>>
>> Who puts u-boot.bin there? Already our in-tree U-Boot recipe / version?
>> I don't recall the details anymore, but such a change appear to me like
>> it requires synchronization.
>>
>
> In this case it is the u-boot package in debian-ports (which now also
> supports “sifive_unmatched”).
>
> http://deb.debian.org/debian-ports/pool-riscv64/main/u/u-boot/u-boot-sifive_2021.07+dfsg-2+b1_riscv64.deb
>
<http://deb.debian.org/debian-ports/pool-riscv64/main/u/u-boot/u-boot-sifive_2021.07+dfsg-2+b1_riscv64.deb>
>
>> or to be more precise, upstream u-boot changed it:
https://github.com/u-boot/u-boot/commit/ae2d9506a36ce2a31b2865c7071e3d20aa633340
> —Tim
>
>>
>>
>> > Signed-off-by: Tim Orling <ticotimo@gmail.com>
>> > ---
>> > meta-isar/recipes-bsp/opensbi/files/sifive-fu540-rules | 2 +-
>> > ...{opensbi-sifive-fu540_0.8.bb => opensbi-sifive-fu540_0.9.bb} | 2 +-
>> > 2 files changed, 2 insertions(+), 2 deletions(-)
>> > rename meta-isar/recipes-bsp/opensbi/{opensbi-sifive-fu540_0.8.bb =>
>> opensbi-sifive-fu540_0.9.bb} (86%)
>> >
>> > diff --git a/meta-isar/recipes-bsp/opensbi/files/sifive-fu540-rules
>> b/meta-isar/recipes-bsp/opensbi/files/sifive-fu540-rules
>> > index c3fc50a..04e5b5a 100644
>> > --- a/meta-isar/recipes-bsp/opensbi/files/sifive-fu540-rules
>> > +++ b/meta-isar/recipes-bsp/opensbi/files/sifive-fu540-rules
>> > @@ -6,7 +6,7 @@ endif
>> >
>> > override_dh_auto_build:
>> > CFLAGS= LDFLAGS= $(MAKE) $(PARALLEL_MAKE) PLATFORM=sifive/fu540 \
>> > - FW_PAYLOAD_PATH=/usr/lib/u-boot/sifive_fu540/u-boot.bin
>> > +
>> FW_PAYLOAD_PATH=/usr/lib/u-boot/sifive_unleashed/u-boot.bin
>> >
>> > %:
>> > dh $@
>> > diff --git a/meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.8.bb
>> b/meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.9.bb
>> > similarity index 86%
>> > rename from meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.8.bb
>> > rename to meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.9.bb
>> > index eb2e206..c25215b 100644
>> > --- a/meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.8.bb
>> > +++ b/meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_0.9.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] =
>> "17e048ac765e92e15f7436b604452614cf88dc2bcbbaab18cdc024f3fdd4c575"
>> > +SRC_URI[sha256sum] =
>> "60f995cb3cd03e3cf5e649194d3395d0fe67499fd960a36cf7058a4efde686f0"
>> >
>> > S = "${WORKDIR}/opensbi-${PV}"
>> >
>> >
>>
>
[-- Attachment #2: Type: text/html, Size: 6662 bytes --]
next prev parent reply other threads:[~2021-09-18 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 19:12 Tim Orling
2021-09-18 6:34 ` Jan Kiszka
2021-09-18 18:05 ` Tim Orling
2021-09-18 18:14 ` Tim Orling [this message]
2021-10-07 6:54 ` 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=CANx9H-DfAChFP_6LvF4oEo33WPjWMUU9-gaihGhL022zaESMGQ@mail.gmail.com \
--to=ticotimo@gmail.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@web.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