From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: defconfig support for CPU_BIG_ENDIAN arm64 kernel
Date: Mon, 23 Nov 2015 23:04:54 +0100 [thread overview]
Message-ID: <62603584.FYAH7ECFA0@wuerfel> (raw)
In-Reply-To: <56538C12.4030506@broadcom.com>
On Monday 23 November 2015 13:58:42 Scott Branden wrote:
> For arm64 platforms there is only a single defconfig upstreamed. This
> builds for Little Endian ARM64 platforms. So...what about Big Endian?
>
> It seems like we need another defconfig with CPU_BIG_ENDIAN to be
> enabled and built in the upstream kernel. We need this deconfig to test
> that drivers compile in big endian mode and we have an upstream kernel
> image to run on these systems.
>
> I'm hoping the upstreamed kernel is already being built/tested with the
> arm64 big endian compiler.
>
> If not, perhaps the upstream solution is to continue to use the single
> defconfig we have today and start using scripts/kconfig/merge_config.sh
> to add the CPU_BIG_ENDIAN support to generate a big endian defconfig?
>
> Hopefully arm64 is already being compiled and tested for Big Endian and
> I'm missing something?
kernelci.org uses Kconfig fragments to build big-endian kernels with
merge-config.sh
We should probably make it a little more straightforward to do this
with mainline kernels. 'make help' already shows 'kvmconfig', 'xenconfig'
and 'tinyconfig' targets for arm64 that use this. Any suggestions how we
should name and integrate big-endian builds?
Arnd
next prev parent reply other threads:[~2015-11-23 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 21:58 defconfig support for CPU_BIG_ENDIAN arm64 kernel Scott Branden
2015-11-23 22:04 ` Arnd Bergmann [this message]
2015-11-23 22:15 ` Scott Branden
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=62603584.FYAH7ECFA0@wuerfel \
--to=arnd@arndb.de \
--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.