> -----Original Message----- > From: Tony Lindgren [mailto:tony@xxxxxxxxxxx] > Sent: Wednesday, April 07, 2010 6:50 AM > 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> [100401 15:54]: > > <snip> > > > > Ref [1] I believe tony has the brand new zoom board - I think your > > > assumption here might be flawed.. > > > > > > > Wait, I just looked up the serial number on the board. The one I was > using > > is a pilot version where this problem exists. > > > > I happen to get an other board which is production unit with ser # > 1013089 > > Rev B. The eMMC on this board has no issue. It reports the EXT_CSD Rev 2 > > which is correct and works fine. > > > > http://omappedia.org/wiki/Zoom_Resources > > > > There is a table here which could help. > > > > Tony, do you care to just look up the serial number of your board? > > Sorry for the delay in replying, I've been travelling for a few weeks > and been in meetings quite a bit. Anyways, it's a 1013037 REV A board, > which seems to be production in the table above. > That means we can not assume all production units have a working eMMC. Would you mind sharing your bootup log? When this device is detected something like below is a clear issue. mmcblk1: mmc1:0001 STM16G 1.00 GiB mmcblk1: p1 p2 Regards, Madhu > > But again there are several boards out there which could have this > > non-working eMMC. So what do we do?? It does not make sense to keep > > something enabled which does not work. > > There's arm kernel parameter for ATAG_REVISION that can be passed from > bootloader and then the board-*.c code can initialize things accordingly > based on the board revision. > > Regards, > > Tony > > > > > [1] http://marc.info/?l=linux-omap&m=126938456103707&w=2 > > -- 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
