> -----Original Message----- > From: Ricardo Salveti [mailto:rsalv...@rsalveti.net] > Sent: Friday, September 10, 2010 8:34 PM > To: Ghorai, Sukumar > Cc: Shilimkar, Santosh; Kevin Hilman; linux-omap@vger.kernel.org; > t...@atomide.com > Subject: Re: [PATCH 0/7] omap4: Fixes, hacks for es2.0 > > On Fri, Sep 10, 2010 at 7:30 AM, Ghorai, Sukumar <s-gho...@ti.com> wrote: > > > > > >> -----Original Message----- > > [..snip..] > >> > >> > >> > >> > The series is boot tested tested on 4430 SDP, Blaze with > >> > >> > omap_4430sdp_defconfig with file over NFS and MMC. > >> > >> > > >> > >> > Also boot tested omap3_defconfig with ramdisk on OMAP4 and OMAP3 > >> > >> > SDPs. Same observation with Panda > >> > >> > > >> > >> > With omap3_defconfig, MMC while mounting the rootfs over MMC, > the > >> > >> > boot hangs. Same observation with Panda > >> > >> > >> > >> On my ES2.0 Panda, rootfs on MMC is now working with this series. > >> > >> > >> > > I observed the same with MMC. Ramdisk boot worked for me on PANDA. > >> > > >> > Note that I said "now working". I think you read my message as "not > >> > working." > >> > > >> Yes I read it otherway ... Second time today :) > >> > >> > IOW, rootfs on MMC *is* working for me on my es2.0 Panda. I applied > >> > your series to current l-o master, and it works. > >> > > >> Cool!! > > > > [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
> > Thanks, > -- > Ricardo Salveti de Araujo -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
