From: Reinhard Meyer <u-boot@emk-elektronik.de>
Date: Mon, 16 Aug 2010 12:16:12 +0200
Subject: [U-Boot] [PATCH v2a]  AT91: add SD/MMC support
In-Reply-To: <6118D856B07F02449C470CE4DA6B1BD3A4035E8078@ise-exchange.ise.de>
References: <4C308A84.2040208@emk-elektronik.de>	<4C602153.8050705@emk-elektronik.de>	<4C6022AC.4020507@emk-elektronik.de>
	<29427373.post@talk.nabble.com> <4C6529C1.10706@emk-elektronik.de>
	<6118D856B07F02449C470CE4DA6B1BD3A4035E8005@ise-exchange.ise.de>
	<4C658F82.2060306@emk-elektronik.de>
	<6118D856B07F02449C470CE4DA6B1BD3A4035E8078@ise-exchange.ise.de>
Message-ID: <4C690FEC.6040506@emk-elektronik.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Dear Schleifer, Alexander,
> But I found out, that the AT91Bootstrap initialization impacts

the U-Boot code. If I use the AT91Bootstrap (without mci initialization)

from NAND flash, the mmc init command successfully reads the card.

It fails if I use the AT91Bootstrap with mci initialization.

That's unlikely (it has the same init sequences)...

Do you have at91_mci_hw_init(void) in your at91samXXXX_devices.c
and do you call that function from your board init?

Can you list me what that bootstrap does initialize differently
if mci is enabled?

Best Regards,
Reinhard