Unless I am mistaken the mmc init vs mmc rescan should not be an issue if the default env in u-boot is correct. As background, legacy mmc drivers need mmc init and new generic mmc drivers need mmc rescan. I agree that this change is annoying, however the difference can be handled in the default env. See the patch "ARMV7: OMAP4: Use generic mmc driver on Beagle" for details:
http://www.sakoman.com/cgi-bin/gitweb.cgi?p=u-boot.git%3Ba=commitdiff%3Bh=cc...
On Thu, Oct 14, 2010 at 3:38 AM, Loïc Minier loic.minier@linaro.org wrote:
On Thu, Oct 14, 2010, Shawn Guo wrote:
Quote from https://bugs.launchpad.net/linaro-image-tools/+bug/659720: Actually, we do not need to add anything before the first "fatload". We set the bootcmd in boot.scr, and boot.scr itself is in mmc boot partition. We have to get mmc ready before doing "fatload boot.scr" in u-boot. In another word, when u-boot runs at the command in boot.scr, the mmc must be already initialized.
So it means we have to track which platforms use which MMC init command; how ugly :-/ is there a way we could test for it?
In fact, I don't understand the need for mmc rescan and mmc init at all; why can't this simply be done when mmc accesses are done?
-- Loïc Minier
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev