diff options
| author | Dirk Behme <[email protected]> | 2011-08-09 07:52:57 +0000 |
|---|---|---|
| committer | Albert ARIBAUD <[email protected]> | 2011-09-04 11:34:00 +0200 |
| commit | 8fcf5959a8dcd92ef01d5e909a5c14581488df93 (patch) | |
| tree | f37749cc793482c39c8da48609476c0b8e572924 /include | |
| parent | 080a46eaf1c2a51cc4df1a4cd3ff2578e64c46b6 (diff) | |
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 <[email protected]>
CC: John Rigby <[email protected]>
CC: Aneesh V <[email protected]>
CC: Sandeep Paulraj <[email protected]>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions
