From patchwork Wed Apr 17 10:02:43 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Russell King - ARM Linux X-Patchwork-Id: 2452911 Return-Path: X-Original-To: patchwork-linux-arm@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork2.kernel.org Received: from casper.infradead.org (casper.infradead.org [85.118.1.10]) by patchwork2.kernel.org (Postfix) with ESMTP id AB68CDF23A for ; Wed, 17 Apr 2013 10:07:00 +0000 (UTC) Received: from merlin.infradead.org ([2001:4978:20e::2]) by casper.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1USPGC-0000oa-F7; Wed, 17 Apr 2013 10:06:40 +0000 Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1USPG3-0000pp-5I; Wed, 17 Apr 2013 10:06:31 +0000 Received: from caramon.arm.linux.org.uk ([78.32.30.218]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1USPFz-0000nX-F3 for linux-arm-kernel@lists.infradead.org; Wed, 17 Apr 2013 10:06:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=arm.linux.org.uk; s=caramon; h=Sender:In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=/9/5rWyhmaA8spPj2IVZ+uYLqNS2zxTf3MMCEVQz7QA=; b=JvSY0T55Nhb5yJ34FDDR/9rQyFLF6yda7QQuk3gy8w1plFRCO74ZLvleIlo0GzkUshLzznxM+N+zvGRD66BQxkiOPErFm/rbbvABS0ft2JZk6RMndwogUbDkITnWFHZonms+mYhO/F7I7TR+qY2HvZl6VGCeIF7tVCHEhPWqwqk=; Received: from n2100.arm.linux.org.uk ([2002:4e20:1eda:1:214:fdff:fe10:4f86]:55086) by caramon.arm.linux.org.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1USPCP-0003dH-9k; Wed, 17 Apr 2013 11:02:45 +0100 Received: from linux by n2100.arm.linux.org.uk with local (Exim 4.76) (envelope-from ) id 1USPCO-0005kO-4j; Wed, 17 Apr 2013 11:02:44 +0100 Date: Wed, 17 Apr 2013 11:02:43 +0100 From: Russell King - ARM Linux To: Chen Gang Subject: Re: [Suggestion] ARM:S5pv210: compiling issue for s5pv210 by using randconfig Message-ID: <20130417100243.GV14496@n2100.arm.linux.org.uk> References: <514FB202.3040807@asianux.com> <515BFA8D.2000204@asianux.com> <20130403101018.GE11040@mudshark.cambridge.arm.com> <515C047A.9010906@asianux.com> <516E6A8E.3000001@asianux.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <516E6A8E.3000001@asianux.com> User-Agent: Mutt/1.5.19 (2009-01-05) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20130417_060628_286558_29C3E34D X-CRM114-Status: GOOD ( 12.94 ) X-Spam-Score: -5.0 (-----) X-Spam-Report: SpamAssassin version 3.3.2 on merlin.infradead.org summary: Content analysis details: (-5.0 points) pts rule name description ---- ---------------------- -------------------------------------------------- -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium trust [78.32.30.218 listed in list.dnswl.org] -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Cc: "kgene.kim@samsung.com" , Will Deacon , "dhowells@redhat.com" , "linux-samsung-soc@vger.kernel.org" , "plagnioj@jcrosoft.com" , "linux-arm-kernel@lists.infradead.org" X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+patchwork-linux-arm=patchwork.kernel.org@lists.infradead.org On Wed, Apr 17, 2013 at 05:25:34PM +0800, Chen Gang wrote: > CONFIG_CPU_ARM7TDMI=y > CONFIG_CPU_ARM9TDMI=y > CONFIG_CPU_V7=y > CONFIG_CPU_32v4T=y > CONFIG_CPU_32v6K=y > CONFIG_CPU_32v7=y This is an invalid configuration. A single kernel can not support ARMv7 and ARMv4T simultaneously. The problem is caused by MMU=n, which exposes the CPU_ARM7TDMI and CPU_ARM9TDMI options, which in turn select 32v4T. This is in turn caused by the incomplete integration of uclinux. I think the only thing which can be done is to remove the ARM9TDMI support code, which doesn't seem to be used by anything, and adjust ARM7TDMI so that it isn't visible, but is selected by ARCH_AT91X40 (which seems to be its only user.) Here's the slightly smaller version of that: diff --git a/arch/arm/mach-at91/Kconfig.non_dt b/arch/arm/mach-at91/Kconfig.non_dt index 6c24985..dc972e1 100644 --- a/arch/arm/mach-at91/Kconfig.non_dt +++ b/arch/arm/mach-at91/Kconfig.non_dt @@ -47,6 +47,7 @@ config ARCH_AT91X40 select ARCH_USES_GETTIMEOFFSET select MULTI_IRQ_HANDLER select SPARSE_IRQ + select CPU_ARM7TDMI endchoice diff --git a/arch/arm/mm/Kconfig b/arch/arm/mm/Kconfig index cb812a1..deb6c6a 100644 --- a/arch/arm/mm/Kconfig +++ b/arch/arm/mm/Kconfig @@ -6,7 +6,7 @@ comment "Processor Type" # ARM7TDMI config CPU_ARM7TDMI - bool "Support ARM7TDMI processor" + bool depends on !MMU select CPU_32v4T select CPU_ABRT_LV4T @@ -56,7 +56,7 @@ config CPU_ARM740T # ARM9TDMI config CPU_ARM9TDMI - bool "Support ARM9TDMI processor" + bool depends on !MMU select CPU_32v4T select CPU_ABRT_NOMMU