From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
Helmut Grohne <helmut@subdivi.de>,
Srinuvasan Arjunan <srinuvasanasv@gmail.com>
Subject: Re: [PATCH 0/9] Restore cross-build for RISC-V, update VisionFive 2
Date: Wed, 3 Jan 2024 17:39:27 +0100 [thread overview]
Message-ID: <b5712785-6119-4d06-b979-db0aabc107e6@siemens.com> (raw)
In-Reply-To: <cover.1704190109.git.jan.kiszka@siemens.com>
On 02.01.24 11:08, 'Jan Kiszka' via isar-users wrote:
> This brings back riscv64 cross-building via a not-so-nice-but-needed
> temporary workaround and uses the outcome for fixing and updating the
> VisionFive 2 to all-upstream.
>
> Jan
>
>
> CC: Helmut Grohne <helmut@subdivi.de>
>
> Jan Kiszka (9):
> crossvars: Account for PACKAGE_ARCH = "${BUILD_ARCH}"
> Add workaround for cross-building riscv64
> meta-isar: jh7110-u-boot-spl-tool: Use BPN instead of PN
> meta-isar: starfive-visionfive2: Use kernel DTB
> meta-isar: jh7110-u-boot-spl-tool: Rework
> meta-isar: starfive-visionfive2: Switch to upstream U-Boot
> meta-isar: starfive-visionfive2: Drop obsolete recipes
> meta-isar: linux-mainline: Update to 6.6.9
> meta-isar: Switch VisionFive 2 to mainline kernel
>
> .../conf/machine/starfive-visionfive2.conf | 15 ++-----
> .../jh7110-u-boot-spl-image/files/install | 1 -
> .../jh7110-u-boot-spl-image/files/rules | 10 -----
> .../jh7110-u-boot-spl-image_0.1.bb | 32 ---------------
> ...l_0.1.bb => jh7110-u-boot-spl-tool_0.2.bb} | 2 +-
> .../opensbi/files/starfive-visionfive2-rules | 12 ++++++
> .../files/starfive-visionfive2-rules.tmpl | 17 --------
> ...ensbi-starfive-visionfive2_1.2+20230310.bb | 11 +----
> .../files/starfive-visionfive2-rules.tmpl | 35 ++++++++++++++++
> ...-starfive-visionfive2_2021.10+VF2-3.0.4.bb | 31 --------------
> .../u-boot-starfive-visionfive2_2023.10.bb | 29 +++++++++++++
> .../files/rules.tmpl | 12 ------
> .../files/visionfive2-u-boot-firmware.install | 1 -
> .../visionfive2-uboot-fit-image.its.tmpl | 41 -------------------
> .../visionfive2-u-boot-firmware.bb | 38 -----------------
> .../linux/files/starfive2_extra.cfg | 6 +--
> ...ine_5.4.203.bb => linux-mainline_6.6.9.bb} | 8 ++--
> .../linux/linux-starfive_5.15-visionfive2.bb | 19 ---------
> .../canned-wks/starfive-visionfive2.wks.in | 4 +-
> meta/classes/crossvars.bbclass | 2 +-
> meta/recipes-devtools/keyutils/keyutils.bb | 13 ++++++
> .../sbuild-chroot/sbuild-chroot-host.bb | 2 +
> 22 files changed, 108 insertions(+), 233 deletions(-)
> delete mode 100644 meta-isar/recipes-bsp/jh7110-u-boot-spl-image/files/install
> delete mode 100644 meta-isar/recipes-bsp/jh7110-u-boot-spl-image/files/rules
> delete mode 100644 meta-isar/recipes-bsp/jh7110-u-boot-spl-image/jh7110-u-boot-spl-image_0.1.bb
> rename meta-isar/recipes-bsp/jh7110-u-boot-spl-tool/{jh7110-u-boot-spl-tool_0.1.bb => jh7110-u-boot-spl-tool_0.2.bb} (85%)
> create mode 100644 meta-isar/recipes-bsp/opensbi/files/starfive-visionfive2-rules
> delete mode 100644 meta-isar/recipes-bsp/opensbi/files/starfive-visionfive2-rules.tmpl
> create mode 100755 meta-isar/recipes-bsp/u-boot/files/starfive-visionfive2-rules.tmpl
> delete mode 100644 meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2021.10+VF2-3.0.4.bb
> create mode 100644 meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2023.10.bb
> delete mode 100644 meta-isar/recipes-bsp/visionfive2-u-boot-firmware/files/rules.tmpl
> delete mode 100644 meta-isar/recipes-bsp/visionfive2-u-boot-firmware/files/visionfive2-u-boot-firmware.install
> delete mode 100644 meta-isar/recipes-bsp/visionfive2-u-boot-firmware/files/visionfive2-uboot-fit-image.its.tmpl
> delete mode 100644 meta-isar/recipes-bsp/visionfive2-u-boot-firmware/visionfive2-u-boot-firmware.bb
> rename meta-isar/recipes-kernel/linux/{linux-mainline_5.4.203.bb => linux-mainline_6.6.9.bb} (82%)
> delete mode 100644 meta-isar/recipes-kernel/linux/linux-starfive_5.15-visionfive2.bb
> create mode 100644 meta/recipes-devtools/keyutils/keyutils.bb
>
Forgot to mention: This series also depends on [1].
That patch not only enables replacing pre-installed (from bootstrap)
packages in the sbuild-chroot, it also allows to install additional ones
from isar-apt - positive side effect.
Jan
[1]
https://groups.google.com/d/msgid/isar-users/9b36ffce-0214-4734-b04a-06475bb0c97c%40siemens.com
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-01-03 16:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 10:08 Jan Kiszka
2024-01-02 10:08 ` [PATCH 1/9] crossvars: Account for PACKAGE_ARCH = "${BUILD_ARCH}" Jan Kiszka
2024-01-02 10:08 ` [PATCH 2/9] Add workaround for cross-building riscv64 Jan Kiszka
2024-01-08 17:31 ` Jan Kiszka
2024-01-02 10:08 ` [PATCH 3/9] meta-isar: jh7110-u-boot-spl-tool: Use BPN instead of PN Jan Kiszka
2024-01-02 10:08 ` [PATCH 4/9] meta-isar: starfive-visionfive2: Use kernel DTB Jan Kiszka
2024-01-02 10:08 ` [PATCH 5/9] meta-isar: jh7110-u-boot-spl-tool: Rework Jan Kiszka
2024-01-02 10:08 ` [PATCH 6/9] meta-isar: starfive-visionfive2: Switch to upstream U-Boot Jan Kiszka
2024-01-02 10:08 ` [PATCH 7/9] meta-isar: starfive-visionfive2: Drop obsolete recipes Jan Kiszka
2024-01-02 10:08 ` [PATCH 8/9] meta-isar: linux-mainline: Update to 6.6.9 Jan Kiszka
2024-01-02 10:08 ` [PATCH 9/9] meta-isar: Switch VisionFive 2 to mainline kernel Jan Kiszka
2024-01-03 16:39 ` Jan Kiszka [this message]
2024-01-05 15:45 ` [PATCH 0/9] Restore cross-build for RISC-V, update VisionFive 2 Anton Mikanovich
2024-01-05 21:19 ` Jan Kiszka
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=b5712785-6119-4d06-b979-db0aabc107e6@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=helmut@subdivi.de \
--cc=isar-users@googlegroups.com \
--cc=srinuvasanasv@gmail.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