From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "Kiszka, Jan" <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: RE: [PATCH 0/6] Starfive VisionFive 2 updates
Date: Thu, 8 Jun 2023 02:57:43 +0000 [thread overview]
Message-ID: <33e03c192e8a4367aba85c8c100ab26e@siemens.com> (raw)
In-Reply-To: <c800d97f-e03c-9034-0073-619205a1e711@siemens.com>
Hi Jan,
Thanks for the fix. Just tested it on the VF2 board and can confirm that it works correctly.
Tested-by Felix Moessbauer <felix.moessbauer@siemens.com>
Felix
-----Original Message-----
From: Kiszka, Jan (T CED) <jan.kiszka@siemens.com>
Sent: Monday, June 5, 2023 2:57 AM
To: isar-users <isar-users@googlegroups.com>
Cc: MOESSBAUER, Felix (T CED INW-CN) <felix.moessbauer@siemens.com>
Subject: Re: [PATCH 0/6] Starfive VisionFive 2 updates
On 04.06.23 18:21, 'Jan Kiszka' via isar-users wrote:
> This first fixes a build issue of the current U-Boot recipe and then
> switches the firmware to upstream U-Boot, simplifying things
> significantly.
There is one catch I missed so far: Upstream is not yet reading out the EEPROM, and that means the MAC addresses are not properly set in the DT.
U-Boot patches are under review [1], currently testing the relevant ones locally. But that may mean we need to keep the legacy version for now and take patch 1 only.
Jan
[1] https://patchwork.ozlabs.org/project/uboot/list/?series=356602
>
> The kernel cannot be switched yet, unfortunately. Already the MMC
> driver is still missing.
>
> Jan
>
> Jan Kiszka (6):
> meta-isar: u-boot-starfive-visionfive2: Fix fetching, update to BSP
> version VF2_v3.0.4
> meta-isar: starfive-visionfive2: Drop IMAGE_INSTALL from machine
> config
> 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
>
> .../conf/machine/starfive-visionfive2.conf | 18 ++------
> .../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 | 5 +--
> .../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 ++++++++++++++++
> ...five-visionfive2_2022.01-rc4+VF2-2.11.5.bb | 31 --------------
> ...u-boot-starfive-visionfive2_2023.07-rc2.bb | 26 ++++++++++++
> .../files/rules.tmpl | 12 ------
> .../files/visionfive2-u-boot-firmware.install | 1 -
> .../visionfive2-uboot-fit-image.its.tmpl | 41 -------------------
> .../visionfive2-u-boot-firmware.bb | 36 ----------------
> .../canned-wks/starfive-visionfive2.wks.in | 6 +--
> 16 files changed, 83 insertions(+), 209 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 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_2022.01-rc4+V
> F2-2.11.5.bb create mode 100644
> meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2023.07-rc2.b
> b 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-ub
> oot-fit-image.its.tmpl delete mode 100644
> meta-isar/recipes-bsp/visionfive2-u-boot-firmware/visionfive2-u-boot-f
> irmware.bb
>
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2023-06-08 2:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 16:21 Jan Kiszka
2023-06-04 16:21 ` [PATCH 1/6] meta-isar: u-boot-starfive-visionfive2: Fix fetching, update to BSP version VF2_v3.0.4 Jan Kiszka
2023-06-12 7:50 ` Jan Kiszka
2023-07-04 10:02 ` Anton Mikanovich
2023-07-04 10:36 ` Jan Kiszka
2023-07-12 7:41 ` Anton Mikanovich
2023-07-12 10:34 ` Jan Kiszka
2023-09-18 8:13 ` Jan Kiszka
2023-09-22 4:38 ` Uladzimir Bely
2023-06-04 16:21 ` [PATCH 2/6] meta-isar: starfive-visionfive2: Drop IMAGE_INSTALL from machine config Jan Kiszka
2023-06-04 16:21 ` [PATCH 3/6] meta-isar: starfive-visionfive2: Use kernel DTB Jan Kiszka
2023-06-04 16:21 ` [PATCH 4/6] meta-isar: jh7110-u-boot-spl-tool: Rework Jan Kiszka
2023-06-04 16:21 ` [PATCH 5/6] meta-isar: starfive-visionfive2: Switch to upstream U-Boot Jan Kiszka
2023-06-04 16:21 ` [PATCH 6/6] meta-isar: starfive-visionfive2: Drop obsolete recipes Jan Kiszka
2023-06-04 18:57 ` [PATCH 0/6] Starfive VisionFive 2 updates Jan Kiszka
2023-06-08 2:57 ` MOESSBAUER, Felix [this message]
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=33e03c192e8a4367aba85c8c100ab26e@siemens.com \
--to=felix.moessbauer@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