bootm: allow omitting entry point for IH_TYPE_KERNEL_NOLOAD

For IH_TYPE_KERNEL_NOLOAD, the entry point is given relative to the
image start, making 0 a valid default, and for IH_OS_EFI, it is ignored
altogether, so it may be preferable to omit it.

Signed-off-by: Nora Schiffer <nora.schiffer@ew.tq-group.com>
Reviewed-by: Simon Glass <sjg@chromium.org>

diff --git a/boot/bootm.c b/boot/bootm.c
index b1cc6fe6c5c3f53a4bbf2b34c4d5cca351096371..1aeabdd5db1102d3eb7f1e98fa5347af4762dd34 100644 (file)
--- a/boot/bootm.c
+++ b/boot/bootm.c
@@ -429,7 +429,7 @@ static int bootm_find_os(const char *cmd_name, const char *addr_fit)
 
                ret = fit_image_get_entry(images.fit_hdr_os,
                                          images.fit_noffset_os, &images.ep);
-               if (ret) {
+               if (ret && images.os.type != IH_TYPE_KERNEL_NOLOAD) {
                        puts("Can't get entry point property!\n");
                        return 1;
                }