From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Heiko Thiery <heiko.thiery@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] configs/kontron_bl_imx8mm_defconfig: new defconfig
Date: Tue, 18 Jan 2022 00:04:48 +0100 [thread overview]
Message-ID: <20220118000448.32ea764d@windsurf> (raw)
In-Reply-To: <752cc85f-d3d6-950b-cb5c-fb39e5020bc3@benettiengineering.com>
On Mon, 17 Jan 2022 20:58:52 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> > diff --git a/configs/kontron_bl_imx8mm_defconfig b/configs/kontron_bl_imx8mm_defconfig
> > new file mode 100644
> > index 0000000000..5b5648cc14
> > --- /dev/null
> > +++ b/configs/kontron_bl_imx8mm_defconfig
> > @@ -0,0 +1,59 @@
> > +# Architecture
> > +BR2_aarch64=y
> > +BR2_ARM_FPU_VFPV3=y
>
> i.MX8MM supports VFPv4-D16, so I would substitute this ^^^ with:
> BR2_ARM_FPU_VFPV4D16
>
> This is to achieve the maximum performance.
Nope, that's not really how it works. VFPv3 is better than VFPv3-D16.
Indeed VFPv3 means that the the FPU has 32 double precision registers,
while VFPv3-D16 means that it has "only" 16 double precision registers.
So, if the i.MX8MM has only the VFPv3-D16, then indeed it should be
chosen, because code compiled with VFPv3 may not work, as it might use
too many double precision registers.
On the other hand, if the i.MX8MM has the full VFPv3, then
BR2_ARM_FPU_VFPV3=y should be used.
That being said, the gcc man page only documents vfpv3, vfpv3-d16-fp16,
vfpv3-fp16 as extension for armv7-a. Interesting, would need to look
into this.
Best regards,
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:[~2022-01-17 23:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 21:15 [Buildroot] [PATCH v2] configs/kontron_bl_imx8mm_defconfig: new defconfig Heiko Thiery
2022-01-14 21:37 ` Giulio Benetti
2022-01-14 21:54 ` Heiko Thiery
[not found] ` <573cda00-7353-2bfd-dbb3-732cd23c5ae4@kontron.de>
2022-01-19 18:23 ` Giulio Benetti
2022-01-17 19:58 ` Giulio Benetti
2022-01-17 23:04 ` Thomas Petazzoni [this message]
2022-01-18 6:58 ` Giulio Benetti
2022-01-18 19:57 ` Heiko Thiery
2022-01-18 20:40 ` Giulio Benetti
2022-01-19 9:01 ` Michael Walle
2022-01-19 9:05 ` 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=20220118000448.32ea764d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=giulio.benetti@benettiengineering.com \
--cc=heiko.thiery@gmail.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.