[PATCH u-boot v2 1/3] aspeed: remove hack loading ramdisk in memory

[Rick Altherr]

See the next patch in this series.  OpenBMC uses ATAGS when building a
legacy image.  U-Boot ATAGS support wasn't causing ramdisk relocation.
It's not really a FIT vs legacy issue so much as a FDT vs ATAGS issue.  We
could still use legacy images with FDT and the ramdisk would be relocated
fine.  I fixed the ATAGS support to trigger ramdisk relocation as that's
the actual bug.

On Mon, Dec 5, 2016 at 12:13 AM, Cédric Le Goater <clg at kaod.org> wrote:

> Hello,
>
> On 12/05/2016 07:24 AM, Simon Glass wrote:
> > On 2 December 2016 at 15:27, Rick Altherr <raltherr at google.com> wrote:
> >> From: Cédric Le Goater <clg at kaod.org>
> >>
> >> Signed-off-by: Cédric Le Goater <clg at kaod.org>
> >> Signed-off-by: Rick Altherr <raltherr at google.com>
> >> ---
> >>  common/image.c | 11 -----------
> >>  1 file changed, 11 deletions(-)
> >
> > Reviewed-by: Simon Glass <sjg at chromium.org>
> >
>
> So how do you fix the ramdisk loading ? is using the FIT images
> enough to work around this problem ?
>
> For legacy type images, this patch seemed to work :
>
>         https://github.com/legoater/u-boot/commit/
> 86fd073a12650ee7fc4e6514f2b0f159be275f29
>
> I am not sure if this is a good approach though.
>
> Thanks,
>
> C.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20161205/2a92d2da/attachment.html>