From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] ARM: add CPU_BE8_BOOT_LE configuration
Date: Wed, 19 Jun 2013 17:29:58 +0100 [thread overview]
Message-ID: <1371659404-20167-2-git-send-email-ben.dooks@codethink.co.uk> (raw)
In-Reply-To: <1371659404-20167-1-git-send-email-ben.dooks@codethink.co.uk>
Add configuration for booting a BE8 system from a LE boot environment.
Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
---
arch/arm/mm/Kconfig | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mm/Kconfig b/arch/arm/mm/Kconfig
index 35955b5..2e1e70f 100644
--- a/arch/arm/mm/Kconfig
+++ b/arch/arm/mm/Kconfig
@@ -688,6 +688,13 @@ config CPU_ENDIAN_BE8
help
Support for the BE-8 (big-endian) mode on ARMv6 and ARMv7 processors.
+config CPU_BE8_BOOT_LE
+ bool "Boot BE system from LE loader"
+ depends on CPU_ENDIAN_BE8
+ help
+ Support for running BE-8 (big-endian) from a boot environment that is
+ running in LE mode.
+
config CPU_ENDIAN_BE32
bool
depends on CPU_BIG_ENDIAN
--
1.7.10.4
next prev parent reply other threads:[~2013-06-19 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 16:29 ARM big-endian - atags and loader updates Ben Dooks
2013-06-19 16:29 ` Ben Dooks [this message]
2013-06-19 17:29 ` [PATCH 1/6] ARM: add CPU_BE8_BOOT_LE configuration Thomas Petazzoni
2013-06-20 10:58 ` Ben Dooks
2013-06-19 16:29 ` [PATCH 2/6] ARM: fixup head for atag verification Ben Dooks
2013-06-19 16:30 ` [PATCH 3/6] ARM: add atag32_to_cpu() function Ben Dooks
2013-06-19 16:30 ` [PATCH 4/6] ARM: update atag-to-fdt code to be endian agnostic Ben Dooks
2013-06-19 16:30 ` [PATCH 5/6] ARM: fixup atags " Ben Dooks
2013-06-19 16:30 ` [PATCH 6/6] ARM: ensure loader information in LE format for BE kernels Ben Dooks
2013-06-27 17:15 ` ARM big-endian - atags and loader updates Ben Dooks
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=1371659404-20167-2-git-send-email-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).