From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guo Ren Subject: Re: [PATCH V2 02/19] csky: defconfig Date: Tue, 3 Jul 2018 16:31:59 +0800 Message-ID: <20180703083157.GA29472@guoren> References: <8c855b4a175fffcb5c897865b7e3d2fe754f0099.1530465326.git.ren_guo@c-sky.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Rob Herring Cc: linux-arch@vger.kernel.org, Linux Kernel Mailing List , Thomas Gleixner , Daniel Lezcano , Jason Cooper , Arnd Bergmann , c-sky_gcc_upstream@c-sky.com, gnu-csky@mentor.com, thomas.petazzoni@bootlin.com, wbx@uclibc-ng.org, Greentime Hu List-Id: linux-arch.vger.kernel.org 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2200-217.mail.aliyun.com ([121.197.200.217]:49576 "EHLO smtp2200-217.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753560AbeGCIcd (ORCPT ); Tue, 3 Jul 2018 04:32:33 -0400 Date: Tue, 3 Jul 2018 16:31:59 +0800 From: Guo Ren Subject: Re: [PATCH V2 02/19] csky: defconfig Message-ID: <20180703083157.GA29472@guoren> References: <8c855b4a175fffcb5c897865b7e3d2fe754f0099.1530465326.git.ren_guo@c-sky.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Rob Herring Cc: linux-arch@vger.kernel.org, Linux Kernel Mailing List , Thomas Gleixner , Daniel Lezcano , Jason Cooper , Arnd Bergmann , c-sky_gcc_upstream@c-sky.com, gnu-csky@mentor.com, thomas.petazzoni@bootlin.com, wbx@uclibc-ng.org, Greentime Hu Message-ID: <20180703083159.Fd0e_v5k-I6XkpX8QfiootJkFgN2WNQvq5Db6p1_YDA@z> 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