On Fri, May 31, 2013 at 10:18:46AM -0400, Tom Rini wrote:
> On Wed, Apr 24, 2013 at 04:11:20PM +0530, Sricharan R wrote:
> 
> > The save_boot_params function does not store the data in a
> > always writable area. So the code is broken for a 'XIP' boot.
> > This series corrects this by storing it in 'gd' and also
> > adds a 'C' equivalent function for the same. The essential cleanups
> > for the same are added in this.
> > 
> > Tested this on omap5 uevm board with SD/EMMC boot.
> > omap4/5 boards does not have a XIP flash.
> > So yet to test XIP with this series.
> > 
> > Also verfied a MAKEALL for armv7.
> 
> OK, do you have a beaglebone or am335x_evm around?  This switch up
> breaks them, and I'm not sure what's going on.  Part of the issue is
> that the NON_SECURE_SRAM_START/END weren't quite right, but they weren't
> so wrong as to be a problem (END wasn't quite the end, and start was in
> the middle of our image, but we didn't reference it).  I'm going to keep
> poking at this as well.  Thanks!

Answered my own question now, am33xx (andti81xx) doesn't opt-in for
omap-common/hwinit-common.c

-- 
Tom

Attachment: signature.asc
Description: Digital signature

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to