>From: Abraham V. [mailto:abraham.varric...@vvdntech.com]
>
>4. At this point we'll get some complaints about missing static
>definitions, so apply the following patch to add them in the common
>configuration file;
>
>diff --git a/include/configs/omap4_common.h b/include/configs/omap4_common.h
>
T
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/a
>
> Plz pull the patch mentioned above, and much of things should be cleaned up
> http://lists.denx.de/pipermail/u-boot/2013-November/167696.html
>
Thank you for the reply Pekon, but sadly even after applying your
patch the earlier compile issue is still present. Starting from a copy
of mainline u
From: Abraham V. [mailto:abraham.varric...@vvdntech.com]
> 1. Added NAND as a configuration option in boards.cfg
>
Yes this is correct ..
[...]
> 2. Added NAND support in omap4_common.h configuration file
> as below (Just copied the lines from am335x_evm.h
> --- a/include/configs/omap4_common
Hello all,
(cc Pekon - my efforts are based on his earlier commit)
My firm is developing an omap4-based board with NAND memory as a boot
option. For the most part it's identical to the pandaboard (OMAP4460)
without most of the peripheral interfaces. After a recent commit which
generalized the omap
5 matches
Mail list logo
