From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
Helmut Grohne <helmut@subdivi.de>,
Srinuvasan Arjunan <srinuvasanasv@gmail.com>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH 0/9] Restore cross-build for RISC-V, update VisionFive 2
Date: Fri, 5 Jan 2024 17:45:34 +0200 [thread overview]
Message-ID: <3033ffbc-6254-4d59-92ca-9e6241f39469@ilbers.de> (raw)
In-Reply-To: <b5712785-6119-4d06-b979-db0aabc107e6@siemens.com>
03/01/2024 18:39, 'Jan Kiszka' via isar-users wrote:
> 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
>
This patchset not just add cross-build of RISC-V, but also fix non-cross
building of starfive-visionfive2:example-module.
On the other hand 'Restore support' patch will influence on isar-apt usage
quite a lot and should be tested more carefully. We've experienced several
failed CI builds with this changes but can't say for sure if commit was the
reason.
We are trying to avoid unstable changes before the release.
That's why I propose to merge RISC-V related changes first. At least to fix
non-cross startfive-visionfive2 building.
next prev parent reply other threads:[~2024-01-05 15:45 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 ` [PATCH 0/9] Restore cross-build for RISC-V, update VisionFive 2 Jan Kiszka
2024-01-05 15:45 ` Anton Mikanovich [this message]
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=3033ffbc-6254-4d59-92ca-9e6241f39469@ilbers.de \
--to=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=helmut@subdivi.de \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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