From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: yann.morin@orange.com
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Conor Dooley <Conor.Dooley@microchip.com>,
buildroot@buildroot.org,
Valentina Fernandez Alanis
<Valentina.FernandezAlanis@microchip.com>,
Jamie Gibbons <jamie.gibbons@microchip.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v2 1/3] arch/Config.in.riscv: update instruction set ext
Date: Thu, 17 Aug 2023 11:45:04 +0200 [thread overview]
Message-ID: <20230817114504.58473b4e@windsurf> (raw)
In-Reply-To: <ZN3Z6ixzNKiu2JbS@tl-lnx-nyma7486-2>
Hello,
On Thu, 17 Aug 2023 10:27:22 +0200
yann.morin@orange.com wrote:
> With the change Yann@home suggests, it makes it obvious and visible that
> generic forces IMAFD, without having to guess (or look at generic's help
> to see what symbols it selects).
Ah, I see what you propose. Yes, it also makes sense.
> However, why do we want to expose those extra sets (C, V) to be optional
> for generic? Isn't that really in fact just defining a custom silicon,
> which is the reason we have a "custom" choice to begin with?
>
> Or do we want to interpret "generic" as "base", e.g. "base that is able
> to run a Linux system without too much hurdle, anything else less
> featured will not cope very well at build or runtime, or may restrict
> the set of packages you may enable; you may enable further extensions" ?
That was my idea indeed. To me "G" is a shortcut for IMAFD, but
potentially you can have extra extensions as well.
> Note that G is anyway a superset of IMAFD, as it also contains the Zicsr
> and Zifencei extensions. In Buildroot, as for the I set, we expect those
> two extensions to always be available (see arch/arch.mk.riscv@33 and
> commit d479264b34f2).
Agreed.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-17 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 9:24 [Buildroot] [PATCH v2 0/3] Update RISC-V Instruction Sets Jamie Gibbons via buildroot
2023-08-16 9:24 ` [Buildroot] [PATCH v2 1/3] arch/Config.in.riscv: update instruction set ext Jamie Gibbons via buildroot
2023-08-16 12:23 ` Thomas Petazzoni via buildroot
2023-08-16 15:04 ` Yann E. MORIN
2023-08-17 7:40 ` Thomas Petazzoni via buildroot
2023-08-17 8:27 ` yann.morin
2023-08-17 9:45 ` Thomas Petazzoni via buildroot [this message]
2023-08-16 9:24 ` [Buildroot] [PATCH v2 2/3] configs/microchip_mpfs_icicle_defconfig: update instruction sets Jamie Gibbons via buildroot
2023-08-16 9:24 ` [Buildroot] [PATCH v2 3/3] board/microchip/mpfs_icicle: update post-image script Jamie Gibbons 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=20230817114504.58473b4e@windsurf \
--to=buildroot@buildroot.org \
--cc=Conor.Dooley@microchip.com \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=jamie.gibbons@microchip.com \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
--cc=yann.morin@orange.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.