From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] arch/arm: use EABIhf by default with VFP
Date: Mon, 26 Oct 2015 09:25:36 +0100 [thread overview]
Message-ID: <20151026092536.6aa7996b@free-electrons.com> (raw)
In-Reply-To: <87bnbmdqad.fsf@dell.be.48ers.dk>
Peter,
On Mon, 26 Oct 2015 08:47:54 +0100, Peter Korsgaard wrote:
> > However, unlike BR2_ARM_CPU_HAS_NEON which gets selected even on ARM
> > cores for which NEON is optional, but for which the user has explicitly
> > requested NEON support to be enabled (through BR2_ARM_ENABLE_NEON), it
> > is not the case for the VFP option. I think we should do that.
> > Otherwise, BR2_ARM_CPU_HAS_VFPV2 will not be true, even if the VFPv2
> > unit is actually available and used.
>
> But packages should use the BR2_ARM_FPU_VFPV2 (and 3/4) symbols to check
> if they should use the VFP, and not BR2_ARM_CPU_MAYBE_HAS_VFPV2 || BR2_ARM_CPU_HAS_VFPV2
But then they have to test BR2_ARM_FPU_VFPV2 || BR2_ARM_FPU_VFPV3 ||
BR2_ARM_FPU_VFPV3D16 || ...
If they just want to know if a VFP is available.
> I don't think kconfig will let us both have these options depend on
> BR2_ARM_CPU_MAYBE_HAS_VFPV2 || BR2_ARM_CPU_HAS_VFPV2 and select
> BR2_ARM_CPU_HAS_VFPV2.
Indeed, it doesn't. Some better solution is needed :)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-26 8:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 22:23 [Buildroot] rpi: image generation Benoît Thébaudeau
2015-08-20 7:59 ` Thomas Petazzoni
2015-08-20 14:30 ` Vivien Didelot
2015-08-22 20:01 ` [Buildroot] [PATCH 1/4] configs/raspberrypi: use EABIhf Benoît Thébaudeau
2015-08-22 20:01 ` [Buildroot] [PATCH 2/4] board/raspberrypi: prepare the image files for the target Benoît Thébaudeau
2015-10-17 11:45 ` Yann E. MORIN
2015-10-17 13:52 ` Benoît Thébaudeau
2015-08-22 20:01 ` [Buildroot] [PATCH 3/4] board/raspberrypi: generate a medium image Benoît Thébaudeau
2015-08-22 20:01 ` [Buildroot] [PATCH 4/4] board/raspberrypi: auto-expand rootfs on first boot Benoît Thébaudeau
2015-08-27 9:02 ` Benoît Thébaudeau
2015-08-27 21:22 ` Jérôme Pouiller
2015-08-28 10:36 ` Benoît Thébaudeau
2015-08-28 11:15 ` Benoît Thébaudeau
[not found] ` <4057940.fE2DsQZqLb@sagittea>
2015-08-31 9:11 ` Benoît Thébaudeau
2015-08-31 12:17 ` Floris Bos
2015-08-31 18:53 ` Benoît Thébaudeau
2015-08-31 13:25 ` Floris Bos
2015-08-31 19:05 ` Benoît Thébaudeau
2015-10-12 21:59 ` [Buildroot] [PATCH 1/4] configs/raspberrypi: use EABIhf Thomas Petazzoni
2015-10-12 23:17 ` Benoît Thébaudeau
2015-10-13 7:06 ` Arnout Vandecappelle
2015-10-15 20:11 ` Peter Korsgaard
2015-10-15 21:12 ` Peter Korsgaard
2015-10-25 15:19 ` [Buildroot] [PATCH] arch/arm: use EABIhf by default with VFP Benoît Thébaudeau
2015-10-25 18:53 ` Peter Korsgaard
2015-10-26 0:32 ` Thomas Petazzoni
2015-10-26 7:47 ` Peter Korsgaard
2015-10-26 8:25 ` Thomas Petazzoni [this message]
2015-10-26 8:51 ` Peter Korsgaard
2015-10-25 18:55 ` Peter Korsgaard
2015-10-25 20:27 ` Benoît Thébaudeau
2015-10-25 20:40 ` Peter Korsgaard
2015-10-25 20:52 ` Benoît Thébaudeau
2015-10-25 21:30 ` 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=20151026092536.6aa7996b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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