From patchwork Wed Apr 17 10:53:20 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Arnd Bergmann X-Patchwork-Id: 2452991 Return-Path: X-Original-To: patchwork-linux-samsung-soc@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork2.kernel.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by patchwork2.kernel.org (Postfix) with ESMTP id 37488DF23A for ; Wed, 17 Apr 2013 10:56:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936321Ab3DQK4G (ORCPT ); Wed, 17 Apr 2013 06:56:06 -0400 Received: from moutng.kundenserver.de ([212.227.126.186]:63666 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936303Ab3DQK4F (ORCPT ); Wed, 17 Apr 2013 06:56:05 -0400 Received: from klappe2.localnet (HSI-KBW-095-208-002-043.hsi5.kabel-badenwuerttemberg.de [95.208.2.43]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0Lar3w-1UqiBF2fbU-00kjQ6; Wed, 17 Apr 2013 12:53:21 +0200 From: Arnd Bergmann To: Will Deacon Subject: Re: [Suggestion] ARM:S5pv210: compiling issue for s5pv210 by using randconfig Date: Wed, 17 Apr 2013 12:53:20 +0200 User-Agent: KMail/1.12.2 (Linux/3.8.0-18-generic; KDE/4.3.2; x86_64; ; ) Cc: Chen Gang , "Russell King - ARM Linux" , "dhowells@redhat.com" , "plagnioj@jcrosoft.com" , "kgene.kim@samsung.com" , "linux-samsung-soc@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" References: <514FB202.3040807@asianux.com> <516E6A8E.3000001@asianux.com> <20130417100136.GB19492@mudshark.cambridge.arm.com> In-Reply-To: <20130417100136.GB19492@mudshark.cambridge.arm.com> MIME-Version: 1.0 Message-Id: <201304171253.20284.arnd@arndb.de> X-Provags-ID: V02:K0:Fl54dpWTMSGYkFk13dK4W42zolcWdxtbLxC0zSN/sfn ADU/9eSMYedFCnFTtf//ncXv+kDNTF7XhcqAfipO5mKt+hohO9 tAcoqftiCB2yZHUs0tRuLpJ7zYpxx4/C0PPJ0Bmu4z6dDxZCCV 6zN0FaEiPmN0X4kucLnANoAikl/oSuQwx01bodC6S3bAmT/Btq nn7GnZNJb+ktxVRa9NSpDtTRlI/b5Qk3jib28XJPc5ApKWk/2m ycZjNCgaK2ihgrM+12nd0aSKXJwJ3rjHy1k3xyaX98ebvDnIFO +tVvbA67FQj4ftAxGupAMtItTNMe088CHr50+kx/nPlvR8a4ro enSnSofQAcwhoyR6dJvw= Sender: linux-samsung-soc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-samsung-soc@vger.kernel.org On Wednesday 17 April 2013, Will Deacon wrote: > > arm-linux-gnu-gcc -Wp,-MD,arch/arm/vfp/.vfphw.o.d -nostdinc -isystem /usr/lib/gcc/arm-linux-gnueabi/4.7.1/include -I/root/linux-next/arch/arm/include -Iarch/arm/include/generated -Iinclude -I/root/linux-next/arch/arm/include/uapi -Iarch/arm/include/generated/uapi -I/root/linux-next/include/uapi -Iinclude/generated/uapi -include /root/linux-next/include/linux/kconfig.h -D__KERNEL__ -mlittle-endian -Iarch/arm/mach-s5pv210/include -Iarch/arm/plat-samsung/include -D__ASSEMBLY__ -mabi=apcs-gnu -mno-thumb-interwork -marm -D__LINUX_ARM_ARCH__=4 -march=armv4t -mtune=arm9tdmi -include asm/unified.h -Wa,-mfpu=softvfp+vfp -mfloat-abi=soft -c -o arch/arm/vfp/vfphw.o arch/arm/vfp/vfphw.S > > > > > > compiling err: > > > > arch/arm/vfp/vfphw.S: Assembler messages: > > arch/arm/vfp/vfphw.S:295: Error: selected processor does not support ARM mode `mrrc p11,3,r0,r1,c0' > > arch/arm/vfp/vfphw.S:295: Error: selected processor does not support ARM mode `mrrc p11,3,r0,r1,c1' > > The problem here is that you've ended up targetting a platform (s5pv210) > that selects CPU_V7. VFP is then subsequently selected, but CONFIG_MMU=n, so > 7TDMI and 9TDMI (v4 CPUs, no VFP) are selectable. Selecting either of those, > causes these warnings. > > Unfortunately, I'm not sure how best to fix this. Most of the !MMU CPUs are > tied to a particular board (lots of `if ARCH_INTEGRATOR' predicates), but we > don't want to do that for 7tdmi. > > If we could enforce the strict exclusion of {<= ARMv5} and {ARMv6+} in the > Kconfig, that would solve your problem. I have not tried to get no-MMU kernels to build in general. I think the way it should be done is to not offer any user-selectable CPU types at all but always select the CPU from the board. For randconfig tests, I would recommend turning on CONFIG_MMU unconditionally using an appropriate KCONFIG_ALLCONFIG= file. The alternative is to use the patch below, but it may be incomplete: I could not find anything other than AT91x40 in the kernel that actually has an ARM7TDMI or ARM9TDMI. Arnd --- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html 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 84af266..c5e4ef0 100644 --- a/arch/arm/mm/Kconfig +++ b/arch/arm/mm/Kconfig @@ -6,7 +6,6 @@ comment "Processor Type" # ARM7TDMI config CPU_ARM7TDMI - bool "Support ARM7TDMI processor" depends on !MMU select CPU_32v4T select CPU_ABRT_LV4T @@ -56,7 +55,6 @@ config CPU_ARM740T # ARM9TDMI config CPU_ARM9TDMI - bool "Support ARM9TDMI processor" depends on !MMU select CPU_32v4T select CPU_ABRT_NOMMU