[U-Boot] image: Use ENOENT instead of ENOMEDIUM for better compatibility

Jeroen Hofstee
2013-06-16T17:17:24Z

Hello Simon,

On 06/16/2013 04:46 PM, Simon Glass wrote:
> This error may not be defined on some platforms such as MacOS so host
> compilation will fail. Use one of the more common errors instead.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
>
> ---
> common/image-fit.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/common/image-fit.c b/common/image-fit.c
> index 7bf82d3..f40f160 100644
> --- a/common/image-fit.c
> +++ b/common/image-fit.c
> @@ -1557,7 +1557,7 @@ int fit_image_load(bootm_headers_t *images, const char *prop_name, ulong addr,
> if (fit_image_get_data(fit, noffset, &buf, &size)) {
> printf("Could not find %s subimage data!\n", prop_name);
> bootstage_error(bootstage_id + BOOTSTAGE_SUB_GET_DATA);
> - return -ENOMEDIUM;
> + return -ENOENT;
> }
> len = (ulong)size;
>
This fixes building for FreeBSD as well, thanks.

Regards,
Jeroen