common/cmd_fdt.c · e9455fcc4526bb354150655876b8badab8a8c2ea · Jack Humbert / reform-boundary-uboot

Forked from Reform / reform-boundary-uboot

34481 commits behind the upstream repository.

12 years ago

fdt: Check if the FDT address is configured · e02c9458

Marek Vasut authored 12 years ago


In case the "fdt addr" command wasn't ran yet and any other "fdt"
subcommand was issued, the system crashed due to NULL pointer being
used.

This is caused by "fdt addr" command setting up a pointer to the
FDT memory location. Prior issuing "fdt addr", the pointer is NULL
so calling any other subcommands crashed the u-boot.

Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Simon Glass <sjg@chromium.org>

e02c9458

History

fdt: Check if the FDT address is configured

Marek Vasut authored 12 years ago


In case the "fdt addr" command wasn't ran yet and any other "fdt"
subcommand was issued, the system crashed due to NULL pointer being
used.

This is caused by "fdt addr" command setting up a pointer to the
FDT memory location. Prior issuing "fdt addr", the pointer is NULL
so calling any other subcommands crashed the u-boot.

Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Simon Glass <sjg@chromium.org>

cmd_fdt.c 20.55 KiB