summaryrefslogtreecommitdiff
path: root/cmd
diff options
context:
space:
mode:
authorAndre Przywara <andre.przywara@arm.com>2022-10-10 20:01:21 +0300
committerTom Rini <trini@konsulko.com>2022-10-21 23:06:14 +0300
commit2f6c45eb6870989372d62afa365380aa44448bf3 (patch)
treed42568bda02feea2ac8a2f9d6906276b797aeb95 /cmd
parent163fb376695661620f13839ec35d860e7e7ff504 (diff)
downloadu-boot-2f6c45eb6870989372d62afa365380aa44448bf3.tar.xz
qfw: return failure when no kernel could be loaded
When we try to load a kernel via the QEMU firmware device, we currently "return -1;" if no kernel was specified on the QEMU command line. This leads to the usage output, which is confusing (since nothing on the command line was really wrong), but also somewhat hides the actual error message. Return CMD_RET_FAILURE (1), as it's a proper error, and make the message more clear that this is not only a "warning". This helps to call this command in boot scripts, and to gracefully continue if this doesn't work. Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Diffstat (limited to 'cmd')
-rw-r--r--cmd/qfw.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/cmd/qfw.c b/cmd/qfw.c
index c61001b771..95ddc4b79e 100644
--- a/cmd/qfw.c
+++ b/cmd/qfw.c
@@ -26,8 +26,8 @@ static int qemu_fwcfg_cmd_setup_kernel(void *load_addr, void *initrd_addr)
qfw_read_entry(qfw_dev, FW_CFG_KERNEL_SIZE, 4, &kernel_size);
if (kernel_size == 0) {
- printf("warning: no kernel available\n");
- return -1;
+ printf("fatal: no kernel available\n");
+ return CMD_RET_FAILURE;
}
data_addr = load_addr;