Check firmware_fdt_addr header to see if it
is a valid fdt blob.

Signed-off-by: Rick Chen <r...@andestech.com>
Reviewed-by: Leo Yu-Chi Liang <ycli...@andestech.com>
---
 board/AndesTech/ax25-ae350/ax25-ae350.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/board/AndesTech/ax25-ae350/ax25-ae350.c 
b/board/AndesTech/ax25-ae350/ax25-ae350.c
index 36f0dd4b0f..08d0c6b264 100644
--- a/board/AndesTech/ax25-ae350/ax25-ae350.c
+++ b/board/AndesTech/ax25-ae350/ax25-ae350.c
@@ -60,7 +60,7 @@ void *board_fdt_blob_setup(int *err)
        *err = 0;
 
        if (IS_ENABLED(CONFIG_OF_SEPARATE) || IS_ENABLED(CONFIG_OF_BOARD)) {
-               if (gd->arch.firmware_fdt_addr)
+               if (fdt_magic((void *)gd->arch.firmware_fdt_addr) == FDT_MAGIC)
                        return (void *)(ulong)gd->arch.firmware_fdt_addr;
        }
 
-- 
2.18.0

Reply via email to