On Thursday 31 January 2013 04:10 PM, Russell King - ARM Linux wrote:
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.
I just tried latest mainline (commit: 04c2eee5) and default config
just boots fine.
I was looking at your build system output which shows the boot
state "OMAP4430 SDP: fail". Your config seems to be with
CONFIG_ARCH_MULTIPLATFORM=y and indeed this kernel doesn't
boot. Seems to abort very early in boot. Am looking at it.
Regards,
Santosh
P.S Btw, the load address issue with multi-platform build
was highlighted on the list in past by Tony [1]
[1] http://www.spinics.net/lists/linux-omap/msg84146.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
