Some people boot images with the entry point in the middle of the blob (like Linux with the head code in discardable .init.text), and there is no no real requirement that the entry point be right after the mkimage header when doing XIP, so let people specify whatever they want. If they do need an entry right after the header, then they still can do that with normal -e behavior.

Signed-off-by: Mike Frysinger vapier@gentoo.org --- tools/mkimage.c | 14 -------------- 1 files changed, 0 insertions(+), 14 deletions(-)

diff --git a/tools/mkimage.c b/tools/mkimage.c index cf4b754..f71f8e7 100644 --- a/tools/mkimage.c +++ b/tools/mkimage.c @@ -283,20 +283,6 @@ NXTARG: ; params.ep += tparams->header_size; }

- /* - * If XIP, ensure the entry point is equal to the load address plus - * the size of the U-Boot header. - */ - if (params.xflag) { - if (params.ep != params.addr + tparams->header_size) { - fprintf (stderr, - "%s: For XIP, the entry point must be the load addr + %lu\n", - params.cmdname, - (unsigned long)tparams->header_size); - exit (EXIT_FAILURE); - } - } - params.imagefile = *argv;

if (params.fflag){