From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3 4/4] arch/arm: update VFPv2 comment to mention ARMv5
Date: Wed, 17 Jul 2013 22:30:50 +0200 [thread overview]
Message-ID: <1374093050-30344-5-git-send-email-thomas.petazzoni@free-electrons.com> (raw)
In-Reply-To: <1374093050-30344-1-git-send-email-thomas.petazzoni@free-electrons.com>
Commit 6b3a0417c4 ('arch/arm: arm926 may have VFP') forgot to update
the help text of the VFPv2 option to mention ARMv5. This commit fixes
that.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
arch/Config.in.arm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/Config.in.arm b/arch/Config.in.arm
index b2fe257..2a0cf45 100644
--- a/arch/Config.in.arm
+++ b/arch/Config.in.arm
@@ -193,8 +193,9 @@ config BR2_ARM_FPU_VFPV2
depends on BR2_ARM_CPU_HAS_VFPV2 || BR2_ARM_CPU_MAYBE_HAS_VFPV2
help
This option allows to use the VFPv2 floating point unit, as
- available in some ARMv6 processors (ARM1136JF-S,
- ARM1176JZF-S and ARM11 MPCore).
+ available in some ARMv5 processors (ARM926EJ-S) and some
+ ARMv6 processors (ARM1136JF-S, ARM1176JZF-S and ARM11
+ MPCore).
Note that this option is also safe to use for newer cores
such as Cortex-A, because the VFPv3 and VFPv4 units are
--
1.8.1.2
next prev parent reply other threads:[~2013-07-17 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 20:30 [Buildroot] [PATCHv3 0/4] EABI vs EABIhf check Thomas Petazzoni
2013-07-17 20:30 ` [Buildroot] [PATCHv3 1/4] toolchain/helpers: don't use the x$(...) = x"value" syntax Thomas Petazzoni
2013-07-17 20:30 ` [Buildroot] [PATCHv3 2/4] toolchain: check ARM EABI vs. EABIhf for external toolchains Thomas Petazzoni
2013-07-17 20:30 ` [Buildroot] [PATCHv3 3/4] toolchain/toolchain-external: don't use x$(...) construct or == Thomas Petazzoni
2013-07-17 20:30 ` Thomas Petazzoni [this message]
2013-07-17 20:46 ` [Buildroot] [PATCHv3 0/4] EABI vs EABIhf check Yann E. MORIN
2013-07-17 21:00 ` Peter Korsgaard
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=1374093050-30344-5-git-send-email-thomas.petazzoni@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