summaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2010-01-25 23:50:11 (GMT)
committerWolfgang Denk <wd@denx.de>2010-03-11 22:50:06 (GMT)
commit1b691bb0c2fa18c9b68f15398ef6c8b9e0c0f3e3 (patch)
treef4232fc7656e75de90881bd92e02cd2e14bcafb9 /tools
parent4b99327a4121a28d2bdb2c2b841f5d97931ae905 (diff)
downloadu-boot-1b691bb0c2fa18c9b68f15398ef6c8b9e0c0f3e3.tar.xz
mkimage: dont force entry point with xip
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>
Diffstat (limited to 'tools')
-rw-r--r--tools/mkimage.c14
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){