> -----Original Message----- > From: Tony Lindgren [mailto:tony@xxxxxxxxxxx] > Sent: Wednesday, May 05, 2010 1:27 PM > To: Madhusudhan > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@xxxxxxxxxxxxxxx; > linux-mmc@xxxxxxxxxxxxxxx > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > * Madhusudhan <madhu.cr@xxxxxx> [100430 09:52]: > > <snip> > > > > > > > > > > > > > Hmm, finally got around looking into this again. Looks like the > mmc > > > > > > is now working on my zoom3 with the current Linus' tree at > commit > > > > > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something > that > > > > > > we had in omap-fixes fixed this. Or maybe some fix for > drivers/mmc? > > > > > > > > > > > > This is with the debug_ll patch applied: > > > > > > > > > > > > https://patchwork.kernel.org/patch/87532/ > > > > > > > > > > For the microSD card, turns out the card I used was flakey. So > > > > > that should explain some of the problems. I'm almost certain > > > > > I tried with two different cards earlier though. In any case, > > > > > let's assume the problem is only the eMMC. > > > > > > > > > Sorry, I did not get a complete picture. Your earlier email said > that > > > with > > > > Linus tree eMMC on your Zoom3 is working. Is that correct? > > > > > > Nope, now the microSD is working, eMMC is not working. > > > > > > > IMHO, an omap level fix can not solve the problem with eMMC because > as I > > > can > > > > see from the log you provided above that a 16G device is detected as > 1G. > > > > This is certainly due to the issue I mentioned earlier. > > > > > > OK > > > > This means that some production boards still have this issue with eMMC. > So > > my patch disables the support for MMC2 on zoom boards. Would you > consider > > that? > > But is it also broken on zoom2? > Yes. > And what about this "Simulate multi mmc card as one big" patch? > Did not get you, what patch are you referring to? Regards, Madhu > Regards, > > Tony -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
