From: Will Deacon <will@kernel.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
John Garry <john.garry@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Olof Johansson <olof@lixom.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Chunrong Guo <chunrong.guo@nxp.com>
Subject: Re: [PATCH 3/3] arm64: configs: unset CPU_BIG_ENDIAN
Date: Mon, 14 Oct 2019 17:24:17 +0100 [thread overview]
Message-ID: <20191014162416.uz33olqhgvzioqdk@willie-the-truck> (raw)
In-Reply-To: <20191012145055.GO25745@shell.armlinux.org.uk>
On Sat, Oct 12, 2019 at 03:50:55PM +0100, Russell King - ARM Linux admin wrote:
> On Sat, Oct 12, 2019 at 12:47:45AM +0200, Arnd Bergmann wrote:
> > On Fri, Oct 11, 2019 at 12:33 PM Russell King - ARM Linux admin
> > <linux@armlinux.org.uk> wrote:
> > > 32-bit ARM experience is that telco class users really like big
> > > endian.
> >
> > Right, basically anyone with a large code base migrated over from a
> > big-endian MIPS or PowerPC legacy that found it cheaper to change
> > the rest of the world than to fix their own code.
>
> I think you need to step off your soap box! Big endian isn't going
> away, and it likely has nothing to do with code bases. Just look at
> networking and telco protocols. Everything in that world tends to
> be big endian. BE is what is understood in that world, and there's
> little we can do to change it.
>
> Demanding that they switch to LE is tantamount to you demanding that
> their entire world change - it ain't going to happen.
Oh, I wasn't demanding anything! Just interested to know if big-endian is
actually being used because it's not something that I'm able to test
sensibly and I haven't see anywhere near the amount of (public) effort to
keep it supported as for little-endian. However, having asked the question,
it's clear that it does have some users so we'll keep maintaining it on a
best-effort basis and rely on those users to let us know if anything breaks.
Will
next prev parent reply other threads:[~2019-10-14 16:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 19:30 [PATCH 0/3] arm64: defconfig: set/unset for allmodconfig Anders Roxell
2019-09-26 19:30 ` [PATCH 1/3] arm64: configs: defconfig: enable DEBUG_PREEMPT and FTRACE Anders Roxell
2019-09-26 19:30 ` [PATCH] arm64: configs: defconfig: remove unneeded fragments Anders Roxell
2019-09-26 19:30 ` [PATCH 2/3] arm64: configs: unset CMDLINE_FORCE Anders Roxell
2019-10-15 8:38 ` John Garry
2019-09-26 19:30 ` [PATCH 3/3] arm64: configs: unset CPU_BIG_ENDIAN Anders Roxell
2019-10-01 14:04 ` John Garry
2019-10-03 7:40 ` Anders Roxell
2019-10-03 11:15 ` John Garry
2019-10-11 10:25 ` Arnd Bergmann
2019-10-11 10:27 ` Will Deacon
2019-10-11 10:33 ` Russell King - ARM Linux admin
2019-10-11 22:47 ` Arnd Bergmann
2019-10-12 14:50 ` Russell King - ARM Linux admin
2019-10-14 16:24 ` Will Deacon [this message]
2019-10-15 3:13 ` Hanjun Guo
2019-10-12 7:33 ` Hanjun Guo
2019-10-12 14:05 ` Arnd Bergmann
2019-10-14 6:12 ` Hanjun Guo
2019-10-14 16:20 ` Will Deacon
2019-10-14 10:58 ` [PATCH 0/3] arm64: defconfig: set/unset for allmodconfig John Garry
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=20191014162416.uz33olqhgvzioqdk@willie-the-truck \
--to=will@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=chunrong.guo@nxp.com \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=olof@lixom.net \
/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).