On Mon, Sep 13, 2010 at 12:06 PM, Ghorai, Sukumar <s-ghorai@xxxxxx> wrote: >> >> > [Ghorai] I have tested MMC/SD boot using omap3_defconfig on ZOOM3, >> 4430 >> >> ES2.0 SDP, Blaze and Panda and all booting fine. >> >> > >> >> > And omap_4430sdp_defconfig also ok omap4. >> >> >> >> Which Panda version are you using during your tests? I tried >> >> omap_4430sdp_defconfig using omap4-for-tony branch at my ES2.0 and I'm >> >> unable to detect the MMC. >> >> >> >> Do I need any other patch to make the MMC work with Panda? >> > [Ghorai] I have tested based on following tree/branch and using ES2.0 >> PANDA only. Can you share bootlog enabling mmc/sd debug message? >> > http://dev.omapzoom.org/?p=santosh/kernel-omap4- >> base.git;a=shortlog;h=refs/heads/omap4-for-tony >> >> My boot log: >> http://paste.ubuntu.com/491645/ >> > [Ghorai] can you use this bootargs? > setenv bootargs root=/dev/mmcblk0p2 rw rootwait mem=463M console=ttyS2,115200n8 > And here is the log from my setup. > [ 2.493194] Waiting for root device /dev/mmcblk0p2... > [ 2.502960] mmc0: host does not support reading read-only switch. assuming write-enable. > [ 2.523895] mmc0: new high speed SDHC card at address e1ed > [ 2.531616] mmcblk0: mmc0:e1ed SD04G 3.75 GiB > [ 2.539550] mmcblk0: p1 p2 > [ 2.607360] EXT3-fs: barriers not enabled > >> Using x-loader from >> http://gitorious.org/pandaboard/x-loader/commits/omap4_panda_L24.9 and >> upstream u-boot. > [Ghorai] can you try with this x-loader > https://docs.google.com/leaf?id=0B8fdjBBEQ4lDZGE3ZTBjNzEtOTQ0Ni00ZmFlLTlhODgtN2QzNjUwMzBkNDI2&hl=en > In the mean time I will try with yours! I'm unable to boot with your x-loader at my ES2.0 (6 and 8 layers), however I'm able to boot it with ES1. Are you sure you're testing it at an ES2 board? This is what I get, it just hangs: Texas Instruments X-Loader 1.41 (Aug 11 2010 - 10:51:13) Could not read bootloader! X-Loader hangs Cheers, -- Ricardo Salveti de Araujo -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
