public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: daniel.bovensiepen@siemens.com, florian.bezdeka@siemens.com
Subject: Re: [PATCH v4 1/6] starfive-visionfive2: package u-boot
Date: Sun, 4 Jun 2023 11:26:25 +0200	[thread overview]
Message-ID: <132f3ed5-590b-d472-1fad-9df0dcb2837c@siemens.com> (raw)
In-Reply-To: <20230410094252.1151370-2-felix.moessbauer@siemens.com>

On 10.04.23 11:42, Felix Moessbauer wrote:
> This patch adds the u-boot firmware for the starfive visionfive2 board.
> As the image is signed at build time, but verified at runtime, we get a
> rather complex cross dependency chain around openssl. To not diverge
> from the official visionfive2 BSP example, we keep the image signing.
> 
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>  ...five-visionfive2_2022.01-rc4+VF2-2.11.5.bb | 31 +++++++++++++++++++
>  1 file changed, 31 insertions(+)
>  create mode 100644 meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2022.01-rc4+VF2-2.11.5.bb
> 
> diff --git a/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2022.01-rc4+VF2-2.11.5.bb b/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2022.01-rc4+VF2-2.11.5.bb
> new file mode 100644
> index 00000000..0eeedc1a
> --- /dev/null
> +++ b/meta-isar/recipes-bsp/u-boot/u-boot-starfive-visionfive2_2022.01-rc4+VF2-2.11.5.bb
> @@ -0,0 +1,31 @@
> +#
> +# Copyright (c) Siemens AG, 2023
> +#
> +# SPDX-License-Identifier: MIT
> +
> +require recipes-bsp/u-boot/u-boot-custom.inc
> +
> +SRC_URI += "git://github.com/starfive-tech/u-boot.git;branch=JH7110_VisionFive2_devel;protocol=https;destsuffix=u-boot-${PV}"
> +SRCREV = "ac0ac696256abf412826d74ee918dd417e207d7b"

This is not a stable reference: JH7110_VisionFive2_devel is rebasing,
and now it left ac0ac696 orphaned behind [1].

Looking at u-boot master, upcoming 2023.07 will support the chip with
theses drivers:

1. ns16550 UART Driver.
2. StarFive JH7110 clock Driver.
3. StarFive JH7110 reset Driver.
4. Cadence QSPI controller Driver.
5. MMC SPI Driver for MMC/SD support.

Wouldn't that be enough for now? USB is missing which might be nice if
booting from an emulated stick but the standard scenarios should work -
and using some U-Boot 2023.07-rcX will not break CI again.

Jan

PS: Your recipe claims to be 2022.01-rc4-something but the U-Boot
baseline is actually 2021.10. Maybe selected the wrong sha?

[1]
https://github.com/starfive-tech/u-boot/commit/ac0ac696256abf412826d74ee918dd417e207d7b

-- 
Siemens AG, Technology
Competence Center Embedded Linux


  reply	other threads:[~2023-06-04  9:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  9:42 [PATCH v4 0/6] Add BSP for StarFiveTech VisionFive2 Risc-V board 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 [this message]
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 ` [PATCH v4 0/6] Add BSP for StarFiveTech VisionFive2 Risc-V board MOESSBAUER, Felix
2023-05-26  7:48   ` 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=132f3ed5-590b-d472-1fad-9df0dcb2837c@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=daniel.bovensiepen@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=isar-users@googlegroups.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