[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a3DBbCeqvQeS4sdG8tzAvvgk72EDA7oDfeQDL1-7bnzkg@mail.gmail.com>
Date: Thu, 16 Nov 2017 11:25:45 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Greentime Hu <green.hu@...il.com>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
Greentime <greentime@...estech.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arch <linux-arch@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Marc Zyngier <marc.zyngier@....com>,
Rob Herring <robh+dt@...nel.org>,
Networking <netdev@...r.kernel.org>,
Vincent Chen <vincentc@...estech.com>
Subject: Re: [PATCH 26/31] nds32: Build infrastructure
On Thu, Nov 16, 2017 at 11:03 AM, Greentime Hu <green.hu@...il.com> wrote:
> 2017-11-13 18:45 GMT+08:00 Geert Uytterhoeven <geert@...ux-m68k.org>:
>> Given the checks for __NDS32_EB__, NDS32 can be either big or little endian,
>> so you should have (excatly one of) CPU_BIG_ENDIAN or CPU_LITTLE_ENDIAN set.
>
> Thanks.
> I will check if we need this config or not and update in the next version patch.
I think we have one architecture in the kernel that determines endianess from
the way that the toolchain is built. What all the others do it to have a Kconfig
option, at least CONFIG_CPU_BIG_ENDIAN that is used to pass -mbig-endian
or -mlittle-endian to the compiler. You should do it that way so you can use
any toolchain with any kernel configuration.
Arnd
Powered by blists - more mailing lists