From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Buildroot List <buildroot@buildroot.org>,
James Hilliard <james.hilliard1@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH 2/5] arch/Config.in: remove BR2_ARCH_HAS_MMU_MANDATORY from BR2_aarch64*
Date: Tue, 19 Apr 2022 23:34:46 +0200 [thread overview]
Message-ID: <20220419213450.887728-2-thomas.petazzoni@bootlin.com> (raw)
In-Reply-To: <20220419213450.887728-1-thomas.petazzoni@bootlin.com>
Selecting BR2_ARCH_HAS_MMU_MANDATORY from BR2_aarch64 and
BR2_aarch64_be doesn't make much sense, because the actual ARM cores
described in arch/Config.in.arm then all select
BR2_ARCH_HAS_MMU_OPTIONAL. So we end up with both
BR2_ARCH_HAS_MMU_OPTIONAL and BR2_ARCH_HAS_MMU_MANDATORY, which
doesn't make any sense.
To prevent this, we remove the selection of BR2_ARCH_HAS_MMU_MANDATORY
from BR2_aarch64 and BR2_aarch64_be, and let arch/Config.in.arm do its
job. What arch/Config.in.arm does is currently incorrect, but it will
be fixed in a separate commit.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
arch/Config.in | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/Config.in b/arch/Config.in
index e51ef60f40..d0d8854c2d 100644
--- a/arch/Config.in
+++ b/arch/Config.in
@@ -60,7 +60,6 @@ config BR2_armeb
config BR2_aarch64
bool "AArch64 (little endian)"
select BR2_ARCH_IS_64
- select BR2_ARCH_HAS_MMU_MANDATORY
help
Aarch64 is a 64-bit architecture developed by ARM Holdings.
http://www.arm.com/products/processors/instruction-set-architectures/armv8-architecture.php
@@ -69,7 +68,6 @@ config BR2_aarch64
config BR2_aarch64_be
bool "AArch64 (big endian)"
select BR2_ARCH_IS_64
- select BR2_ARCH_HAS_MMU_MANDATORY
help
Aarch64 is a 64-bit architecture developed by ARM Holdings.
http://www.arm.com/products/processors/instruction-set-architectures/armv8-architecture.php
--
2.35.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-04-19 21:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 21:34 [Buildroot] [PATCH 1/5] arch/Config.in.sh: fixup MMU selection Thomas Petazzoni via buildroot
2022-04-19 21:34 ` Thomas Petazzoni via buildroot [this message]
2022-04-19 21:34 ` [Buildroot] [PATCH 3/5] arch/Config.in.arm: re-organize " Thomas Petazzoni via buildroot
2022-05-18 20:24 ` Romain Naour
2022-05-18 21:35 ` Thomas Petazzoni via buildroot
2022-05-26 9:49 ` Peter Korsgaard
2022-04-19 21:34 ` [Buildroot] [PATCH 4/5] arch: drop support for SH2A Thomas Petazzoni via buildroot
2022-04-24 8:54 ` Yann E. MORIN
2022-04-19 21:34 ` [Buildroot] [PATCH 5/5] arch/Config.in.sh: move BR2_ARCH_HAS_MMU_MANDATORY one level up Thomas Petazzoni via buildroot
2022-05-26 9:46 ` Peter Korsgaard
2022-04-24 8:56 ` [Buildroot] [PATCH 1/5] arch/Config.in.sh: fixup MMU selection Yann E. MORIN
2022-05-26 9:44 ` 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=20220419213450.887728-2-thomas.petazzoni@bootlin.com \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.