From: "Jon Mason" <jdmason@kudzu.us>
To: openembedded-core@lists.openembedded.org
Subject: [meta-oe][PATCH 2/4] tune-cortexa55.inc: clean-up ARMv8.2a uses
Date: Wed, 9 Sep 2020 18:16:50 -0400 [thread overview]
Message-ID: <20200909221652.6750-3-jon.mason@arm.com> (raw)
In-Reply-To: <20200909221652.6750-1-jon.mason@arm.com>
Remove 'crc', as that is implied by 8.2 (per GCC
https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html#AArch64-Options).
Also, the PACKAGE_EXTRA_ARCHS should refer to the ARMv8.2a version, not
the more generic ARMv8 version.
Signed-off-by: Jon Mason <jon.mason@arm.com>
---
meta/conf/machine/include/tune-cortexa55.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/conf/machine/include/tune-cortexa55.inc b/meta/conf/machine/include/tune-cortexa55.inc
index b383eb733b72..66a5d0c437ee 100644
--- a/meta/conf/machine/include/tune-cortexa55.inc
+++ b/meta/conf/machine/include/tune-cortexa55.inc
@@ -8,6 +8,6 @@ require conf/machine/include/arm/arch-armv8-2a.inc
# Little Endian base configs
AVAILTUNES += "cortexa55"
ARMPKGARCH_tune-cortexa55 = "cortexa55"
-TUNE_FEATURES_tune-cortexa55 = "aarch64 cortexa55 crc crypto"
-PACKAGE_EXTRA_ARCHS_tune-cortexa55 = "${PACKAGE_EXTRA_ARCHS_tune-armv8a-crc-crypto} cortexa55"
+TUNE_FEATURES_tune-cortexa55 = "aarch64 cortexa55 crypto"
+PACKAGE_EXTRA_ARCHS_tune-cortexa55 = "${PACKAGE_EXTRA_ARCHS_tune-armv8-2a-crypto} cortexa55"
BASE_LIB_tune-cortexa55 = "lib64"
--
2.20.1
next prev parent reply other threads:[~2020-09-09 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 22:16 [meta-oe][PATCH 0/4] Arm Tune Clean-Ups Jon Mason
2020-09-09 22:16 ` [meta-oe][PATCH 1/4] cortex-m0plus.inc: change file permissions Jon Mason
2020-09-09 22:16 ` Jon Mason [this message]
2020-09-09 22:16 ` [meta-oe][PATCH 3/4] tune-cortexa57-cortexa53.inc: add CRC and set march Jon Mason
2020-09-09 22:39 ` [OE-core] " Mark Hatle
2020-09-09 22:16 ` [meta-oe][PATCH 4/4] tune-cortexa*: Cleanups Jon Mason
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=20200909221652.6750-3-jon.mason@arm.com \
--to=jdmason@kudzu.us \
--cc=openembedded-core@lists.openembedded.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