[PATCH RFC 2/2] Don't honor initrd load address
Uwe Kleine-König
u.kleine-koenig at pengutronix.de
Thu May 2 05:07:12 EDT 2013
From: Sascha Hauer <s.hauer at pengutronix.de>
U-Boot doesn't honor the load address specified in an initrd. Barebox
shouldn't be more strict here. This unbreaks booting an uInitrd
generated by Debian's flash-kernel that uses 0 as entry address where
there is nothing on the i.MX53 that was used.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig at pengutronix.de>
---
commands/bootm.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/commands/bootm.c b/commands/bootm.c
index bb44776..5dd1703 100644
--- a/commands/bootm.c
+++ b/commands/bootm.c
@@ -127,9 +127,6 @@ static int bootm_open_initrd_uimage(struct image_data *data)
data->initrd = data->os;
}
- if (data->initrd_address == UIMAGE_INVALID_ADDRESS)
- data->initrd_address = data->initrd->header.ih_load;
-
return 0;
}
--
1.8.2.rc2
More information about the barebox
mailing list