Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "kilian.zinnecker--- via buildroot" <buildroot@buildroot.org>
To: kilian.zinnecker@mail.de, buildroot@buildroot.org
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Robert Nelson <robertcnelson@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2 2/2] configs/beaglev_ahead: new defconfig
Date: Sun, 11 Feb 2024 13:24:57 +0100	[thread overview]
Message-ID: <2172310.irdbgypaU6@laptop> (raw)
In-Reply-To: <8f6baf1d-3caa-4b47-aad9-a34fa0761058@benettiengineering.com>

Hello Giulio, all,

> > This patch adds board support for the BeagleV-Ahead. It uses a
> > custom kernel for the board's SoC. As the SoC has an outdated and
> > currently not supported version of the RISC-V vector extension, the
> > vector extension is disabled.
> 
> can you please provide an URL to the product page?

Yes, I added an URL into the commit message of v3.

[--SNIP--]
> > --- /dev/null
> > +++ b/board/beaglev-ahead/post-image.sh
> > @@ -0,0 +1,6 @@
> > +#!/usr/bin/env bash
> > +set -e
> > +
> > +cp -r ${BUILD_DIR}/linux-custom/arch/riscv/boot/dts/thead/overlays/
> > ${BINARIES_DIR}
> linux-custom should substituted with $(LINUX_DIR)

I tried $(LINUX_DIR) and ${LINUX_DIR}, but both resulted in an empty string 
and as a consequence in a wrong path and broke the build. So in my v3 I kept 
it as it is for now. Should I try something else?

> > --- /dev/null
> > +++ b/configs/beaglev_ahead_defconfig
> > @@ -0,0 +1,44 @@
> > +BR2_riscv=y
> > +BR2_riscv_custom=y
> > +BR2_RISCV_ISA_CUSTOM_RVM=y
> > +BR2_RISCV_ISA_CUSTOM_RVA=y
> > +BR2_RISCV_ISA_CUSTOM_RVF=y
> > +BR2_RISCV_ISA_CUSTOM_RVD=y
> > +BR2_RISCV_ISA_CUSTOM_RVC=y
> 
> With commit cbd91e89e43d600172c62fd1cbd33aa74d0a851a all "_CUSTOM" have
> been dropped, so can you please replace all the:
> BR2_RISCV_ISA_CUSTOM_*
> occurences with:
> BR2_RISCV_ISA_*
> ?

I fixed it, thanks.

> > +BR2_GCC_VERSION_13_X=y
> 
> I think there is a reason you force using gcc 13, can you describe it in
> the commit log and here?

Yes, there were problems. I am not 100% sure, but as I remember it: the 
OpenSBI used has an old version and in its build, it does not define certain 
flags, which are needed by GCC 12 to activate the needed zifencei and zicsr 
extension. Those extension where redefined to be in some other extension pack 
of RiscV (or something like that, I don't remeber this exactly). Anyway it 
threw an error in GCC 12, and I thinkt to fix that, one would have to touch the 
old OpenSBI version. Switching to GCC 13 (where it works out of the box) seems 
then to be cleaner for me.

[--SNIP--]
> > +BR2_TARGET_UBOOT_CONFIG_FRAGMENT_FILES="board/beaglev-ahead/uboot.fragmen
> > t" +BR2_TARGET_UBOOT_FORMAT_BIN=y
> > +BR2_TARGET_UBOOT_FORMAT_CUSTOM=y
> > +BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME="u-boot-with-spl.bin"
> 
> Here you need to add:
> BR2_PACKAGE_HOST_DOSFSTOOLS=y
> otherwise it fails to build under buildroot/utils/docker-run

Added dosfstools to the defconfig, thanks!

> > +BR2_PACKAGE_HOST_MTOOLS=y
> > +BR2_PACKAGE_HOST_GENIMAGE=y
> > +BR2_PACKAGE_XUANTIE_BINS=y
> 
> After enabling BR2_RISCV_ISA_ options it builds successfully using
> buildroot/utils/docker-run

I build the image with buildroot/utils/docker-run and it boots. Thanks for the 
hint, I will use buildroot/utils/docker-run in the future as well!

Thanks for your review and best regards,
Kilian




_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-11 12:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 23:12 [Buildroot] [PATCH v2 0/2] Add board support for the BeagleV-Ahead kilian.zinnecker--- via buildroot
2023-12-04 23:12 ` [Buildroot] [PATCH v2 1/2] package/xuantie-bins: new package kilian.zinnecker--- via buildroot
2024-02-06 16:56   ` Giulio Benetti
2024-02-10 15:22     ` kilian.zinnecker--- via buildroot
2024-02-11 12:38       ` Thomas Petazzoni via buildroot
2024-02-11 12:15     ` kilian.zinnecker--- via buildroot
2024-02-13 18:19       ` Giulio Benetti
2023-12-04 23:12 ` [Buildroot] [PATCH v2 2/2] configs/beaglev_ahead: new defconfig kilian.zinnecker--- via buildroot
2024-02-06 16:31   ` Giulio Benetti
2024-02-11 12:24     ` kilian.zinnecker--- via buildroot [this message]
2024-02-13 18:17       ` Giulio Benetti

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=2172310.irdbgypaU6@laptop \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=kilian.zinnecker@mail.de \
    --cc=robertcnelson@gmail.com \
    --cc=thomas.petazzoni@bootlin.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