[PATCH RFC 0/2] Fix uInitrd handling

Uwe Kleine-König u.kleine-koenig at pengutronix.de
Thu May 2 05:07:10 EDT 2013


Hello,

U-Boot doesn't honor the load address of uInitrd images but just places it
somewhere in RAM. So it's sensible to let barebox not being more strict
than U-Boot.

This makes it possible to boot a Debian system on an i.MX53 Loco board
with the setup prepared by flash-kernel. That uInitrd uses a load
address of 0x0 where there is nothing on i.MX53.

This series contains an additional cleanup. I'm not 100% sure it's ok
though. Is it intended that UIMAGE_SOME_ADDRESS being passed to bootm
not being used literally? Should I squash the cleanup in the other
commit? Also a similar simplification might be possible for the load
address of the uImage.

Sascha Hauer (1):
  Don't honor initrd load address

Uwe Kleine-König (1):
  bootm: Simplify initrd address handling

 commands/bootm.c | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

-- 
1.8.2.rc2




More information about the barebox mailing list