From: tushar.jagad@linaro.org (Tushar Jagad)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/4] ARM64: Add Kconfig option to enable Big Endian kernel
Date: Wed, 16 Oct 2013 12:19:28 +0530 [thread overview]
Message-ID: <525E36F8.6080206@linaro.org> (raw)
In-Reply-To: <525D84CF.4060705@codeaurora.org>
Hi Christopher,
On 10/15/2013 11:39 PM, Christopher Covington wrote:
> What makes a board properly built and how can a user determine whether their
> board is?
As of now this flag assumes that the bootloader is in LE mode. It is
left to the kernel to switch to BE mode. This flag makes the kernel set
necessary flags in SCTLR registers on entry.
>
>> + [...] and your board
>> + port must properly enable any big-endian related features
>> + of your chipset/board/processor.
>
> What is a board port for arm64?
This is a generic patch for the architecture. Each driver needs to make
necessary changes keeping the kernel endianness in mind. We have tested
these patches on our X-Gene platform.
--
Regards,
Tushar
next prev parent reply other threads:[~2013-10-16 6:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 12:22 [RFC PATCH 0/4] Big Endian support for ARM64 kernel Ankit Jindal
2013-10-11 12:22 ` [RFC PATCH 1/4] ARM64: Add Kconfig option to enable Big Endian kernel Ankit Jindal
2013-10-15 18:09 ` Christopher Covington
2013-10-16 6:49 ` Tushar Jagad [this message]
2013-10-16 14:30 ` Christopher Covington
2013-10-11 12:22 ` [RFC PATCH 2/4] ARM64: Include appropriate byteorder for Big Endian Ankit Jindal
2013-10-11 12:22 ` [RFC PATCH 3/4] ARM64: Big Endian fixes for kernel booting Ankit Jindal
2013-10-11 12:52 ` Ankit Jindal
2013-10-15 18:24 ` Christopher Covington
2013-10-16 7:04 ` Tushar Jagad
2013-10-11 12:22 ` [RFC PATCH 4/4] ARM64: Support for 32-bit big endian userspace Ankit Jindal
2013-10-15 18:09 ` [RFC PATCH 0/4] Big Endian support for ARM64 kernel Christopher Covington
2013-10-16 8:05 ` Tushar Jagad
2013-10-16 14:40 ` Christopher Covington
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=525E36F8.6080206@linaro.org \
--to=tushar.jagad@linaro.org \
--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).