From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: Failure to boot... Date: Thu, 31 Jan 2013 10:40:44 +0000 Message-ID: <20130131104044.GO2637@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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from caramon.arm.linux.org.uk ([78.32.30.218]:59863 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752858Ab3AaKk5 (ORCPT ); Thu, 31 Jan 2013 05:40:57 -0500 Content-Disposition: inline In-Reply-To: <20130131092024.GN2637@n2100.arm.linux.org.uk> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Nicolas Pitre Cc: Olof Johansson , linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, Tony Lindgren , arm@kernel.org On Thu, Jan 31, 2013 at 09:20:24AM +0000, Russell King - ARM Linux wrote: > On Wed, Jan 30, 2013 at 11:19:40PM -0500, Nicolas Pitre wrote: > > Better yet (IMHO): just enable the zboot command in U-Boot to let you > > boot a zImage binary directly. > > I wish it were that easy but it isn't. I've no idea where to get a > version of uboot for my boards which supports that; TI have always > supplied updates to uboot for me, and with the current state of TI > being afaict in chaos. > > TI have always supplied a replacement X-Loader with each uboot update. > I've no idea what X-Loader is or why both get updated together, but... > > Moreover, I doubt that the 3430LDP, of which there are multiple versions, > will ever see a uboot update. It already suffers from a lack of correct > kernel support due to random wiring changes between these versions (the > keypad doesn't work correctly) and I've yet to indentify which version > it is despite downloading the circuits. So trying to locate the right > uboot will be impossible there. > > So, I'm _stuck_ with uImages for these platforms. Right, so I'm now passing LOADADDR= which allows this to work - and the latest OMAP4430SDP boot result shows almost the same sad broken story.