From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Jamie Gibbons <jamie.gibbons@microchip.com>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Conor Dooley <Conor.Dooley@microchip.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org,
Valentina Fernandez Alanis
<Valentina.FernandezAlanis@microchip.com>
Subject: Re: [Buildroot] [PATCH v3 2/3] configs/microchip_mpfs_icicle_defconfig: update instruction sets
Date: Fri, 18 Aug 2023 23:58:25 +0200 [thread overview]
Message-ID: <20230818215825.GD1134940@scaer> (raw)
In-Reply-To: <20230818104301.403429-3-jamie.gibbons@microchip.com>
Jamie, All,
On 2023-08-18 11:43 +0100, Jamie Gibbons via buildroot spake thusly:
> Update the instruction sets for MPFS icicle kit to mirror the
> configuration update, i.e. It is now classed as a RISC-V G core with
> support for C, IMAFDC.
>
> Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com>
Applied to next, thanks.
Regards,
Yann E. MORIN.
> ---
> configs/microchip_mpfs_icicle_defconfig | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/configs/microchip_mpfs_icicle_defconfig b/configs/microchip_mpfs_icicle_defconfig
> index b2568cae6a..a3b3093982 100644
> --- a/configs/microchip_mpfs_icicle_defconfig
> +++ b/configs/microchip_mpfs_icicle_defconfig
> @@ -1,8 +1,5 @@
> BR2_riscv=y
> -BR2_riscv_custom=y
> -BR2_RISCV_ISA_CUSTOM_RVM=y
> -BR2_RISCV_ISA_CUSTOM_RVF=y
> -BR2_RISCV_ISA_CUSTOM_RVD=y
> +BR2_riscv_g=y
> BR2_RISCV_ISA_CUSTOM_RVC=y
> BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y
> BR2_TARGET_GENERIC_HOSTNAME="mpfs_icicle"
> --
> 2.34.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-18 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 10:42 [Buildroot] [PATCH v3 0/3] Update RISC-V Instruction Sets Jamie Gibbons via buildroot
2023-08-18 10:42 ` [Buildroot] [PATCH v3 1/3] arch/Config.in.riscv: update instruction set ext Jamie Gibbons via buildroot
2023-08-18 21:58 ` Yann E. MORIN
2023-08-18 10:43 ` [Buildroot] [PATCH v3 2/3] configs/microchip_mpfs_icicle_defconfig: update instruction sets Jamie Gibbons via buildroot
2023-08-18 21:58 ` Yann E. MORIN [this message]
2023-08-18 10:43 ` [Buildroot] [PATCH v3 3/3] board/microchip/mpfs_icicle: update post-image script Jamie Gibbons via buildroot
2023-08-18 22:11 ` Yann E. MORIN
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=20230818215825.GD1134940@scaer \
--to=yann.morin.1998@free.fr \
--cc=Conor.Dooley@microchip.com \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=buildroot@buildroot.org \
--cc=jamie.gibbons@microchip.com \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@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