Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jamie.Gibbons--- via buildroot" <buildroot@buildroot.org>
To: <buildroot@buildroot.org>
Cc: Valentina.FernandezAlanis@microchip.com,
	Ludovic.Desroches@microchip.com, Nicolas.Ferre@microchip.com,
	thomas.petazzoni@bootlin.com, Conor.Dooley@microchip.com
Subject: Re: [Buildroot] [PATCH 1/1] configs/microchip_mpfs_icicle_defconfig: fix zicsr build error
Date: Wed, 1 Nov 2023 10:52:51 +0000	[thread overview]
Message-ID: <f66ac6e3bcfe449528e34bc8eed78efd73f4d792.camel@microchip.com> (raw)
In-Reply-To: <20231002105324.2167088-1-jamie.gibbons@microchip.com>

Hi all,

Is there anything missing/stopping this patch from being merged? It
fixes the reported microchip_mpfs_icicle_defconfig build error.

Thanks,
Jamie.

On Mon, 2023-10-02 at 11:53 +0100, Jamie Gibbons wrote:
> Build is failing with an unrecognised opcode error due to missing
> `zicsr` extension requirement. This is introduced with GCC version 12.
> When binutils was updated to v2.38 they updated to the default ISA
> spec
> version 20191213. In this version the original i extension split into
> i,
> Zicsr and Zifencei. A fix for this has been added since U-Boot version
> 2022.01 to detect new Zicsr and Zifencei extensions and enable it when
> needed
> therefore, an updated U-Boot tag to our latest 2023.09 release will
> fix
> this as in our latest release we have updated to U-Boot version
> 2023.07.
> Update the kernel verion in line with the U-Boot release version to
> ensure compatiblities and latest features and fixes are included.
> Remove riscv_g selection as it is now selected by default.
> 
> Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com>
> ---
>  configs/microchip_mpfs_icicle_defconfig | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/configs/microchip_mpfs_icicle_defconfig
> b/configs/microchip_mpfs_icicle_defconfig
> index 54a4d55a5f..1af7a3c474 100644
> --- a/configs/microchip_mpfs_icicle_defconfig
> +++ b/configs/microchip_mpfs_icicle_defconfig
> @@ -1,12 +1,11 @@
>  BR2_riscv=y
> -BR2_riscv_g=y
>  BR2_RISCV_ISA_RVC=y
>  BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y
>  BR2_TARGET_GENERIC_HOSTNAME="mpfs_icicle"
>  BR2_ROOTFS_POST_IMAGE_SCRIPT="board/microchip/mpfs_icicle/post-
> image.sh"
>  BR2_LINUX_KERNEL=y
>  BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
> -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call
> github,linux4microchip,linux,linux-6.1-
> mchp+fpga)/linux4microchip+fpga-2023.06.tar.gz"
> +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call
> github,linux4microchip,linux,linux-6.1-
> mchp+fpga)/linux4microchip+fpga-2023.09.tar.gz"
>  BR2_LINUX_KERNEL_DEFCONFIG="mpfs"
>  BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="board/microchip/mpfs_icicle/l
> inux.fragment"
>  BR2_LINUX_KERNEL_DTS_SUPPORT=y
> @@ -16,7 +15,7 @@ BR2_TARGET_ROOTFS_EXT2_4=y
>  BR2_TARGET_UBOOT=y
>  BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
>  BR2_TARGET_UBOOT_CUSTOM_TARBALL=y
> -BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="$(call github,polarfire-
> soc,u-boot)linux4microchip+fpga-2023.06.tar.gz"
> +BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="$(call github,polarfire-
> soc,u-boot)linux4microchip+fpga-2023.09.tar.gz"
>  BR2_TARGET_UBOOT_BOARD_DEFCONFIG="microchip_mpfs_icicle"
>  BR2_TARGET_UBOOT_CONFIG_FRAGMENT_FILES="board/microchip/mpfs_icicle/u
> boot-fragment-rootfs.config"
>  BR2_TARGET_UBOOT_NEEDS_DTC=y

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

  reply	other threads:[~2023-11-01 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 10:53 [Buildroot] [PATCH 1/1] configs/microchip_mpfs_icicle_defconfig: fix zicsr build error Jamie Gibbons via buildroot
2023-11-01 10:52 ` Jamie.Gibbons--- via buildroot [this message]
2023-11-01 12:56 ` Yann E. MORIN
  -- strict thread matches above, loose matches on Subject: below --
2023-09-19  8:10 Jamie Gibbons via buildroot
2023-09-19  8:41 ` Thomas Petazzoni via buildroot

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=f66ac6e3bcfe449528e34bc8eed78efd73f4d792.camel@microchip.com \
    --to=buildroot@buildroot.org \
    --cc=Conor.Dooley@microchip.com \
    --cc=Jamie.Gibbons@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=Valentina.FernandezAlanis@microchip.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