From mboxrd@z Thu Jan 1 00:00:00 1970 From: linux@arm.linux.org.uk (Russell King - ARM Linux) Date: Thu, 31 Jan 2013 14:16:35 +0000 Subject: Failure to boot... In-Reply-To: <20130131141320.GQ2637@n2100.arm.linux.org.uk> References: <20130131014912.GM2637@n2100.arm.linux.org.uk> <20130131030203.GA8374@quad.lixom.net> <20130131092024.GN2637@n2100.arm.linux.org.uk> <20130131104044.GO2637@n2100.arm.linux.org.uk> <510A6877.9080307@ti.com> <20130131130437.GP2637@n2100.arm.linux.org.uk> <510A78E1.8010308@ti.com> <20130131141320.GQ2637@n2100.arm.linux.org.uk> Message-ID: <20130131141635.GR2637@n2100.arm.linux.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Jan 31, 2013 at 02:13:20PM +0000, Russell King - ARM Linux wrote: > On Thu, Jan 31, 2013 at 07:30:01PM +0530, Santosh Shilimkar wrote: > > Linus' tip(commit: 04c2eee5) + arm-soc for-next boots fine as well. > > The pull request from Tony [1] fixed the multi-platform boot issue > > for OMAP. > > > > Now trying to merge your for-next and test. > > Well, my tip (which is based on Linus' 6abb7c25) also builds and > boots fine. > > Hang on... > > # CONFIG_ARCH_OMAP2PLUS is not set > CONFIG_ARCH_VEXPRESS=y > > which of course won't boot, and this happens on both oldconfigs because > of the change to multiplatform support. And no, the instructions given last time around to add: # 13 Jan 2013: Update for OMAP moving to multiplatform CONFIG_ARCH_MULTIPLATFORM=y CONFIG_ARCH_MULTI_V7=y don't fix it either, it needs more options defined...