From: Russell King - ARM Linux Subject: Re: [PATCH] OMAP_LDP: Support LCD display as a FB device on ZOOM MDK (Re: LDP support) Date: Mon, 18 May 2009 17:09:57 +0100 Message-ID: <20090518160957.GD7042@n2100.arm.linux.org.uk> References: <5A47E75E594F054BAF48C5E4FC4B92AB030555A7D9@dbde02.ent.ti.com> <4A03F8DD.4070307@windriver.com> <87hbzv8rua.fsf@litku.valot.fi> <20090516081904.GB15328@n2100.arm.linux.org.uk> <87ljoube3z.fsf@litku.valot.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from caramon.arm.linux.org.uk ([78.32.30.218]:36484 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756985AbZERQKW (ORCPT ); Mon, 18 May 2009 12:10:22 -0400 Content-Disposition: inline In-Reply-To: <87ljoube3z.fsf@litku.valot.fi> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Kalle Valo Cc: "stanley.miao" , "Gadiyar, Anand" , Tony Lindgren , "linux-omap@vger.kernel.org" , Imre Deak , Tomi Valkeinen , jon-hunter@ti.com On Mon, May 18, 2009 at 06:54:56PM +0300, Kalle Valo wrote: > Russell King - ARM Linux writes: > > > On Fri, May 08, 2009 at 07:47:09PM +0300, Kalle Valo wrote: > >> "stanley.miao" writes: > >> > >> >> Looks like you used the CodeSourcery 2007q3 toolchain. This had been > >> >> reported earlier. Switching to 2008q3 works. > >> > > >> > Yeah, Now the kernel booted. it's compiler's problem. > >> > >> I was bitten by the same problem few weeks ago. Any chance of getting a > >> warning/error if using 2007q3 compiler until the problem is fixed? > > > > Is there any way of detecting the 2007q3 compiler? > > > > With normal GCC versions, you can use __GNUC__, __GNUC_MINOR__ and > > __GNUC_PATCHLEVEL__ to identify the three digit version number. > > I don't know, most probably not. But Jon Hunter investigated the issue > and he found the issue was related to CONFIG_ARCH_WANT_FRAME_POINTERS: > > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg12403.html > > So maybe we can fix or workaround this. Why does this change anything? FRAME_POINTERS seems to be enabled anyway (and should be given the Kconfig setup we have.)