From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Bovensiepen, Daniel (bovi)" <daniel.bovensiepen@siemens.com>,
"Bezdeka, Florian" <florian.bezdeka@siemens.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH v4 0/6] Add BSP for StarFiveTech VisionFive2 Risc-V board
Date: Fri, 26 May 2023 05:14:15 +0000 [thread overview]
Message-ID: <4c7c99c436d055b0d1dfb36be15b45d577ef1318.camel@siemens.com> (raw)
In-Reply-To: <20230410094252.1151370-1-felix.moessbauer@siemens.com>
Dear maintainers,
are there any news on this series?
Can we merge it?
Best regards,
Felix
On Mon, 2023-04-10 at 09:42 +0000, Felix Moessbauer wrote:
> Changes since v3:
>
> - rebased onto next
> - drop "u-boot: make KCFLAGS and HOSTCFLAGS configurable"
> - opensbi: update version
> - u-boot
> - update which makes patches obsolete
> - support to compile without cross
> - simplify build dependencies
> - remove KCFLAGS injection
> - spl_tool: replace with OSS version from StarFive
> - linux: update which makes patches obsolete
>
> Changes since v2:
>
> - rebased onto next
> - rework u-boot customization (p1)
> - update opensbi
> - update kernel
>
> Changes since v1:
>
> - rebased onto next (including bitbake 2.0 migration)
> - exclude opensbi memory range in u-boot DT
> - use upstream OpenSBI version (instead of StarFive version)
>
> This series adds a new machine "starfive-visionfive2" which is a
> Risc-V board based on the JH7110 SoC. The BSP is modeled based on the
> buildroot SDK [1], but without any proprietary imaging components.
>
> Further, we implement the fit + efi boot toolchain, instead of the
> proposed ubootenv + fit version. This also requires that we embed the
> board's linux device tree into the fit, as memory and reserved-memory
> nodes are resolved via the efi API (implemented by u-boot) instead of
> resolving them via the DT in Linux.
>
> As the JH7110 SoC has no usable upstream support yet, we directly
> build the 5.15 based kernel from the SDK, instead of porting patches
> on top of the standard Linux. Distro kernels are also not supported.
>
> Best regards,
> Felix Moessbauer
> Siemens AG
>
> Felix Moessbauer (6):
> starfive-visionfive2: package u-boot
> starfive-visionfive2: package opensbi firmware
> starfive-visionfive2: add BSP kernel
> starfive-visionfive2: create u-boot-spl firmware
> starfive-visionfive2: create u-boot-spl FIT image
> starfive-visionfive2: add machine
>
> meta-isar/conf/local.conf.sample | 1 +
> .../conf/machine/starfive-visionfive2.conf | 29 +++++++++++++
> .../starfive-visionfive2-sid-ports.conf | 7 ++++
> .../jh7110-u-boot-spl-image/files/install | 1 +
> .../jh7110-u-boot-spl-image/files/rules | 10 +++++
> .../jh7110-u-boot-spl-image_0.1.bb | 30 ++++++++++++++
> .../jh7110-u-boot-spl-tool_0.1.bb | 23 +++++++++++
> .../files/starfive-visionfive2-rules.tmpl | 17 ++++++++
> ...ensbi-starfive-visionfive2_1.2+20230310.bb | 31 ++++++++++++++
> ...five-visionfive2_2022.01-rc4+VF2-2.11.5.bb | 31 ++++++++++++++
> .../files/rules.tmpl | 12 ++++++
> .../files/visionfive2-u-boot-firmware.install | 1 +
> .../visionfive2-uboot-fit-image.its.tmpl | 41
> +++++++++++++++++++
> .../visionfive2-u-boot-firmware.bb | 36 ++++++++++++++++
> .../linux/files/starfive2_extra.cfg | 3 ++
> .../linux/linux-starfive_5.15-visionfive2.bb | 17 ++++++++
> .../canned-wks/starfive-visionfive2.wks.in | 23 +++++++++++
> 17 files changed, 313 insertions(+)
> create mode 100644 meta-isar/conf/machine/starfive-visionfive2.conf
> create mode 100644 meta-isar/conf/multiconfig/starfive-visionfive2-
> sid-ports.conf
> create mode 100644 meta-isar/recipes-bsp/jh7110-u-boot-spl-
> image/files/install
> create mode 100644 meta-isar/recipes-bsp/jh7110-u-boot-spl-
> image/files/rules
> create mode 100644 meta-isar/recipes-bsp/jh7110-u-boot-spl-
> image/jh7110-u-boot-spl-image_0.1.bb
> create mode 100644 meta-isar/recipes-bsp/jh7110-u-boot-spl-
> tool/jh7110-u-boot-spl-tool_0.1.bb
> create mode 100644 meta-isar/recipes-bsp/opensbi/files/starfive-
> visionfive2-rules.tmpl
> create mode 100644 meta-isar/recipes-bsp/opensbi/opensbi-starfive-
> visionfive2_1.2+20230310.bb
> create mode 100644 meta-isar/recipes-bsp/u-boot/u-boot-starfive-
> visionfive2_2022.01-rc4+VF2-2.11.5.bb
> create mode 100644 meta-isar/recipes-bsp/visionfive2-u-boot-
> firmware/files/rules.tmpl
> create mode 100644 meta-isar/recipes-bsp/visionfive2-u-boot-
> firmware/files/visionfive2-u-boot-firmware.install
> create mode 100644 meta-isar/recipes-bsp/visionfive2-u-boot-
> firmware/files/visionfive2-uboot-fit-image.its.tmpl
> create mode 100644 meta-isar/recipes-bsp/visionfive2-u-boot-
> firmware/visionfive2-u-boot-firmware.bb
> create mode 100644 meta-isar/recipes-
> kernel/linux/files/starfive2_extra.cfg
> create mode 100644 meta-isar/recipes-kernel/linux/linux-
> starfive_5.15-visionfive2.bb
> create mode 100644 meta-isar/scripts/lib/wic/canned-wks/starfive-
> visionfive2.wks.in
>
next prev parent reply other threads:[~2023-05-26 5:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 9:42 Felix Moessbauer
2023-04-10 9:42 ` [PATCH v4 1/6] starfive-visionfive2: package u-boot Felix Moessbauer
2023-06-04 9:26 ` Jan Kiszka
2023-04-10 9:42 ` [PATCH v4 2/6] starfive-visionfive2: package opensbi firmware Felix Moessbauer
2023-04-10 9:42 ` [PATCH v4 3/6] starfive-visionfive2: add BSP kernel Felix Moessbauer
2023-04-10 9:42 ` [PATCH v4 4/6] starfive-visionfive2: create u-boot-spl firmware Felix Moessbauer
2023-04-10 9:42 ` [PATCH v4 5/6] starfive-visionfive2: create u-boot-spl FIT image Felix Moessbauer
2023-04-10 9:42 ` [PATCH v4 6/6] starfive-visionfive2: add machine Felix Moessbauer
2023-05-26 5:14 ` MOESSBAUER, Felix [this message]
2023-05-26 7:48 ` [PATCH v4 0/6] Add BSP for StarFiveTech VisionFive2 Risc-V board Uladzimir Bely
2023-05-27 10:41 ` Uladzimir Bely
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=4c7c99c436d055b0d1dfb36be15b45d577ef1318.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=daniel.bovensiepen@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
--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