
3 Jun
2009
3 Jun
'09
1:09 a.m.
On 10:56 Thu 28 May , Andy Fleming wrote:
On Fri, May 22, 2009 at 7:27 PM, Jean-Christophe PLAGNIOL-VILLARD plagnioj@jcrosoft.com wrote:
On 03:56 Wed 20 May , Ilya Yanok wrote: > Signed-off-by: Ilya Yanok <yanok@emcraft.com> > --- > lib_arm/board.c | 7 +++++++ > 1 files changed, 7 insertions(+), 0 deletions(-) > > diff --git a/lib_arm/board.c b/lib_arm/board.c > index 5d05d9b..268532f 100644 > --- a/lib_arm/board.c > +++ b/lib_arm/board.c > @@ -48,6 +48,7 @@ > #include <serial.h> > #include <nand.h> > #include <onenand_uboot.h> > +#include <mmc.h> > > #ifdef CONFIG_DRIVER_SMC91111 > #include "../drivers/net/smc91111.h" > @@ -439,6 +440,12 @@ extern void davinci_eth_set_mac_addr (const u_int8_t *addr); > #ifdef BOARD_LATE_INIT > board_late_init (); > #endif > + > +#ifdef CONFIG_GENERIC_MMC > + puts ("MMC: "); > + mmc_initialize (gd->bd); > +#endif do you use a embedded mmc? otherwise I'll prefer to not init the mmc at the board init but on need
This is the same way ethernet is initialized. mmc_initialize should not perform any SD/MMC transactions, but should set up the driver, and register with the MMC subsystem. Without doing this, there's no way to address the MMC device from the command line...
ok
Best Regards, J.