If we do nand device 0 command in u-boot on a device that has NAND support
enabled but no NAND chip, we can get data abort at least on omaps.

Fix the issue by adding a check for nand_info[dev].

Signed-off-by: Tony Lindgren <t...@atomide.com>
--- a/cmd/nand.c
+++ b/cmd/nand.c
@@ -116,7 +116,7 @@ free_dat:
 static int set_dev(int dev)
 {
        if (dev < 0 || dev >= CONFIG_SYS_MAX_NAND_DEVICE ||
-           !nand_info[dev]->name) {
+           !nand_info[dev] || !nand_info[dev]->name) {
                puts("No such device\n");
                return -1;
        }
-- 
2.9.3

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to