Ghorai, Sukumar had written, on 04/01/2010 01:34 PM, the following:
-----Original Message-----
From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-
owner@xxxxxxxxxxxxxxx] On Behalf Of Chikkature Rajashekar, Madhusudhan
Sent: 2010-04-01 05:56
To: tony@xxxxxxxxxxx
Cc: linux-omap@xxxxxxxxxxxxxxx; linux-mmc@xxxxxxxxxxxxxxx
Subject: [PATCH] Disable the non working eMMC on Zoom2/3
From: Madhusudhan Chikkature <madhu.cr@xxxxxx>
Date: Wed, 31 Mar 2010 12:29:19 -0400
Subject: [PATCH] Zoom2/3: Disable MMC
The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the
writes to fail since the card size is not detected correctly by the
MMC
core. Disable the MMC2 support for Zoom2/3.
[Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the
exact
problem. Because we never face any issue for eMMC in ZOOM3. Because we
have the same eMMC device in 3630-SDP and could have the same problem.
On Zoom3 the EXT_CSD Rev reported by eMMC is zero. See the log attached.
Hence the failures which are reported by people on the list. I had already
bought this problem up on the list previously and was discussed, right?
From the log you can also see that a 16GB device is detected as a 1GB.
[Ghorai] I feel it's an issue with eMMC in pilot-board. And production-board is working fine. And I feel outside TI people having production board only. And 16GB eMMC device is a very good size to work with different things. Otherwise we are talking about MMC#2 boot, eMMC boot, 16GB eMMC device in zoom,.. all these information in different page/ link looks very misleading information, if really having such problem.
I the mean time I will check this in Pilot board too and think you checked in pilot board only.
Ref [1] I believe tony has the brand new zoom board - I think your
assumption here might be flawed..
--
Regards,
Nishanth Menon
Ref:
[1] http://marc.info/?l=linux-omap&m=126938456103707&w=2
--
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
