Hi Stefan, >From: Stefan Roese [mailto:s...@denx.de] > >Commit a0a37183 (ARM: omap: merge GPMC initialization code for all >platform) broke NAND on OMAP3 based platforms. I noticed this while >testing the latest 2014.07-rc version on the TAO3530 board. NAND >detection did not work with this error message: > >NAND: nand: error: Unable to find NAND settings in GPMC Configuration - >quitting > >As OMAP3 configs don't set CONFIG_NAND but CONFIG_NAND_CMD. the GPMC >was not initialized for NAND at all. This patch now fixes this issue. > Sorry couldn't understand this, why have users enabled CONFIG_NAND_CMD, if CONFIG_NAND itself is not enabled ? Otherwise, if TAO3530 board uses the on-die NAND, then it should enable NAND in its board profile via boards.cfg
>Tested on TAO3530 board. with regards, pekon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
