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: Mon, 18 Nov 2013 12:06:18 -0800 [thread overview]
Message-ID: <528A733A.6040304@nvidia.com> (raw)
In-Reply-To: <1384714221.1974.276@driftwood>
Hi Rob,
On 11/17/2013 10:50 AM, Rob Landley wrote:
> On 10/30/2013 11:27:07 AM, Paul Walmsley wrote:
>> 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.
> Annotating the global Documentation/Changes with every per-arch
> requirement... not sure that's the right place for it.
It doesn't matter to me where it's documented in the kernel
documentation, but we should document it.
And we should expect folks who post patches with new toolchain
constraints to also send patches for that documentation...
> Noting armv7 requirements in
> an arm-specific file makes sense. Annotating the top level one raises
> the question of why not to do that for arc, unicore, openrisc, tile...
Yes - it's the following x86-specific text in Documentation/Changes that
inspired the patch:
-----
Linux on IA-32 has recently switched from using as86 to using gas for
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.
-----
But we can move that to Documentation/x86/ also.
regards,
- Paul
next prev parent reply other threads:[~2013-11-18 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 16:27 [PATCH] Documentation/Changes: update binutils version requirement for ARMv7 builds Paul Walmsley
2013-10-30 16:51 ` 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 [this message]
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=528A733A.6040304@nvidia.com \
--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 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.