[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180703083157.GA29472@guoren>
Date: Tue, 3 Jul 2018 16:31:59 +0800
From: Guo Ren <ren_guo@...ky.com>
To: Rob Herring <robh@...nel.org>
Cc: linux-arch@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Jason Cooper <jason@...edaemon.net>,
Arnd Bergmann <arnd@...db.de>, c-sky_gcc_upstream@...ky.com,
gnu-csky@...tor.com, thomas.petazzoni@...tlin.com,
wbx@...ibc-ng.org, Greentime Hu <green.hu@...il.com>
Subject: Re: [PATCH V2 02/19] csky: defconfig
On Mon, Jul 02, 2018 at 09:16:27PM -0600, Rob Herring wrote:
>
> Are these configs mutually exclusive? We try to have one kernel build
> serve many platforms. So you'd probably want to divide things between
> the 2 ABIs.
Yes, they are mutually exclusive, and may I prepare defconfigs like
these:
abiv1_defconfig
abiv2_defconfig (ck807 ck810 ck860 are also mutually exclusive in
-mcpu=ck807/ck810/ck860, you need "make menuconfig" to select correct CPU,
so they couldn't be determined from DT. just like ARMv5, ARMv7-A and
ARMv7-M)
> It looks like you still have lots of options enabled that I wouldn't
> expect you to need. Start with something more minimal for what you
> need to boot and support upstream.
Ok, I'll clean them up in next version patch.
> For a full config, you can use allmodconfig at least to build test.
Thx for the tip.
Guo Ren
Powered by blists - more mailing lists