public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 0/8] Fix and update VisionFive 2
Date: Thu, 01 Feb 2024 14:47:07 +0300	[thread overview]
Message-ID: <f1bff248b801ae3aadce4689753cb90353745e13.camel@ilbers.de> (raw)
In-Reply-To: <cover.1705490373.git.jan.kiszka@siemens.com>

On Wed, 2024-01-17 at 12:19 +0100, 'Jan Kiszka' via isar-users wrote:
> Debian has fixed riscv64 cross-building in sid, and we can now use
> the
> chance to fix and update VisionFive 2. We can't go fully upstream
> with
> that board yet as it would otherwise lack USB and PCIe support. But
> there is a working for-upstream kernel branch on top of 6.6 that we
> can
> use. In contrast, firmware is fully upstream now.
> 
> Changes in v3:
>  - go back to downstream kernel
>  - drop linux-mainline update
>  - update u-boot to 2024.01
>  - update to opensbi 1.4
> 
> Changes in v2:
>  - drop no longer need cross-build workaround
>  - update to kernel 6.6.10
> 
> Jan
> 
> Jan Kiszka (8):
>   crossvars: Account for PACKAGE_ARCH = "${BUILD_ARCH}"
>   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
>   opensbi-starfive-visionfive2: Update to 1.4 release
>   meta-isar: starfive-visionfive2: Drop obsolete recipes
>   linux-starfive: Update to 6.6 upstream queue
> 
>  .../conf/machine/starfive-visionfive2.conf    | 13 ++----
>  .../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 | 33 ---------------
>  .../opensbi-starfive-visionfive2_1.4.bb       | 25 +++++++++++
>  .../files/starfive-visionfive2-rules.tmpl     | 35 ++++++++++++++++
>  ...-starfive-visionfive2_2021.10+VF2-3.0.4.bb | 31 --------------
>  .../u-boot-starfive-visionfive2_2024.01.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 -----------------
>  ...sure-GP-relative-addressing-is-not-u.patch | 32 +++++++++++++++
>  .../linux/files/starfive2_extra.cfg           |  6 ++-
>  .../linux/linux-starfive_5.15-visionfive2.bb  | 19 ---------
>  .../linux/linux-starfive_6.6-visionfive2.bb   | 21 ++++++++++
>  .../canned-wks/starfive-visionfive2.wks.in    |  6 +--
>  meta/classes/crossvars.bbclass                |  2 +-
>  22 files changed, 167 insertions(+), 251 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
>  delete mode 100644 meta-isar/recipes-bsp/opensbi/opensbi-starfive-
> visionfive2_1.2+20230310.bb
>  create mode 100644 meta-isar/recipes-bsp/opensbi/opensbi-starfive-
> visionfive2_1.4.bb
>  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_2024.01.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
>  create mode 100644 meta-isar/recipes-kernel/linux/files/0001-riscv-
> efistub-Ensure-GP-relative-addressing-is-not-u.patch
>  delete mode 100644 meta-isar/recipes-kernel/linux/linux-
> starfive_5.15-visionfive2.bb
>  create mode 100644 meta-isar/recipes-kernel/linux/linux-
> starfive_6.6-visionfive2.bb
> 
> -- 
> 2.35.3
> 

Applied to next, thanks.

  parent reply	other threads:[~2024-02-01 11:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 11:19 Jan Kiszka
2024-01-17 11:19 ` [PATCH v3 1/8] crossvars: Account for PACKAGE_ARCH = "${BUILD_ARCH}" Jan Kiszka
2024-01-17 11:19 ` [PATCH v3 2/8] meta-isar: jh7110-u-boot-spl-tool: Use BPN instead of PN Jan Kiszka
2024-01-17 11:19 ` [PATCH v3 3/8] meta-isar: starfive-visionfive2: Use kernel DTB Jan Kiszka
2024-01-17 11:19 ` [PATCH v3 4/8] meta-isar: jh7110-u-boot-spl-tool: Rework Jan Kiszka
2024-01-17 11:19 ` [PATCH v3 5/8] meta-isar: starfive-visionfive2: Switch to upstream U-Boot Jan Kiszka
2024-01-17 11:19 ` [PATCH v3 6/8] opensbi-starfive-visionfive2: Update to 1.4 release Jan Kiszka
2024-01-17 11:19 ` [PATCH v3 7/8] meta-isar: starfive-visionfive2: Drop obsolete recipes Jan Kiszka
2024-01-17 11:19 ` [PATCH v3 8/8] linux-starfive: Update to 6.6 upstream queue Jan Kiszka
2024-02-01 11:47 ` Uladzimir Bely [this message]
2024-02-01 13:28   ` [PATCH v3 0/8] Fix and update VisionFive 2 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=f1bff248b801ae3aadce4689753cb90353745e13.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --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