From: pwalmsley@nvidia.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Documentation/Changes: update binutils version requirement for ARMv7 builds
Date: Wed, 30 Oct 2013 09:27:07 -0700 [thread overview]
Message-ID: <alpine.DEB.2.02.1310300923080.12006@tamien> (raw)
ARMv7 builds now make use of the pldw opcode and the ".arch_extension mp"
pragma. These aren't supported in binutils prior to 2.21. So, update
Documentation/Changes accordingly.
Signed-off-by: Paul Walmsley <pwalmsley@nvidia.com>
Cc: Will Deacon <will.deacon@arm.com>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: Stephen Warren <swarren@nvidia.com>
Cc: Thierry Reding <treding@nvidia.com>
Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>
---
Intended for 3.13.
Documentation/Changes | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/Changes b/Documentation/Changes
index b175808..97fcbdf 100644
--- a/Documentation/Changes
+++ b/Documentation/Changes
@@ -67,6 +67,9 @@ assembling the 16-bit boot code, removing the need for as86 to compile
your kernel. This change does, however, mean that you need a recent
release of binutils.
+ARMv7 builds require binutils 2.21 or later due to the use of the pldw
+opcode and ".arch_extension mp".
+
Perl
----
--
1.8.1.5
next reply other threads:[~2013-10-30 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 16:27 Paul Walmsley [this message]
2013-10-30 16:51 ` [PATCH] Documentation/Changes: update binutils version requirement for ARMv7 builds Russell King - ARM Linux
2013-11-17 18:50 ` Rob Landley
2013-11-18 16:56 ` Stephen Warren
2013-12-05 2:26 ` Rob Landley
2013-11-18 20:06 ` Paul Walmsley
2013-12-05 2:37 ` Rob Landley
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=alpine.DEB.2.02.1310300923080.12006@tamien \
--to=pwalmsley@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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