aboutsummaryrefslogtreecommitdiff
path: root/tools/omapimage.c
diff options
context:
space:
mode:
authorDirk Behme <dirk.behme@googlemail.com>2011-08-09 07:52:57 +0000
committerAlbert ARIBAUD <albert.u.boot@aribaud.net>2011-09-04 11:34:00 +0200
commit8fcf5959a8dcd92ef01d5e909a5c14581488df93 (patch)
treef37749cc793482c39c8da48609476c0b8e572924 /tools/omapimage.c
parent080a46eaf1c2a51cc4df1a4cd3ff2578e64c46b6 (diff)
downloadu-boot-8fcf5959a8dcd92ef01d5e909a5c14581488df93.zip
u-boot-8fcf5959a8dcd92ef01d5e909a5c14581488df93.tar.gz
u-boot-8fcf5959a8dcd92ef01d5e909a5c14581488df93.tar.bz2
mkimage: Fix 'Unknown OMAP image type - 5'
Using mkimage with e.g. tools/mkimage -A arm -T firmware -O u-boot -d u-boot.bin foo.img gives a warning "Unknown OMAP image type - 5" while it seems that the image itself is created successfully. This does come from the patch "mkimage: Add OMAP boot image support". The method check_image_type in image_type_params is supposed to just return success or failure. However, for omap it also calls fprintf: static int omapimage_check_image_types(uint8_t type) { if (type == IH_TYPE_OMAPIMAGE) return EXIT_SUCCESS; else { fprintf(stderr, "Unknown OMAP image type - %x", type); return EXIT_FAILURE; } } All the other image checkers and no others have this, so the fix is to simply remove the fprintf. Signed-off-by: Dirk Behme <dirk.behme@googlemail.com> CC: John Rigby <john.rigby@linaro.org> CC: Aneesh V <aneesh@ti.com> CC: Sandeep Paulraj <s-paulraj@ti.com>
Diffstat (limited to 'tools/omapimage.c')
-rw-r--r--tools/omapimage.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/tools/omapimage.c b/tools/omapimage.c
index 29d91cc..5e739ac 100644
--- a/tools/omapimage.c
+++ b/tools/omapimage.c
@@ -49,7 +49,6 @@ static int omapimage_check_image_types(uint8_t type)
if (type == IH_TYPE_OMAPIMAGE)
return EXIT_SUCCESS;
else {
- fprintf(stderr, "Unknown OMAP image type - %x", type);
return EXIT_FAILURE;
}
}