[U-Boot] adding NAND support for omap4 (based on pandaboard)

Abraham V. abraham.varricatt at vvdntech.com
Fri Nov 29 13:44:33 CET 2013


Hello Pekon,

An addendum to my last mail; I tried digging into the build mechanism
and finally got the system to build without errors with the following
patch,

diff --git a/arch/arm/cpu/armv7/omap-common/Makefile
b/arch/arm/cpu/armv7/omap-common/Makefile
index 4d3a165..5eeecce 100644
--- a/arch/arm/cpu/armv7/omap-common/Makefile
+++ b/arch/arm/cpu/armv7/omap-common/Makefile
@@ -22,8 +22,6 @@ obj-y += boot-common.o
 obj-y  += lowlevel_init.o
 endif

-ifndef CONFIG_SPL_BUILD
 ifneq ($(CONFIG_OMAP44XX)$(CONFIG_OMAP54XX),)
 obj-y  += mem-common.o
 endif
-endif


The way I understood the compiler error, it was due to a missing
gpmc_init() function. Which, in the case of the OMAP4 and OMAP5 series
appears to be defined in the
"arch/arm/cpu/armv7/omap-common/mem-common.c" file.

For reasons I do not understand, this has been left aside for the SPL
(or MLO ?) builds. Any idea why this is so? What might be the
after-affects of enabling it (like I'm doing)?

Way I see the OMAP4 processor, if you want NAND support, you'll need
GPMC enabled too.

-Abraham


More information about the U-Boot mailing list