linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: madhu.cr@ti.com (Madhusudhan)
To: linux-arm-kernel@lists.infradead.org
Subject: mmc errors (was Re: [PATCH] arm: Fix DEBUG_LL for omap zoom2/3)
Date: Wed, 24 Mar 2010 10:31:08 -0500	[thread overview]
Message-ID: <000001cacb67$0687bef0$544ff780@am.dhcp.ti.com> (raw)
In-Reply-To: <4BA94564.8030803@ti.com>

Hi Nishant,

The eMMC on Zoom2 has an issue with respect to detection as a high capacity
card. This was discussed on the list with Pierre sometime back. I don't have
an acceptable solution to make this device work. Rather I prefer to submit a
patch which disables MMC2 on these boards.

You can still use MMC1 to mount your file system. This is the card you can
plug in to the cage.

Regards,
Madhu

> -----Original Message-----
> From: Nishanth Menon [mailto:nm at ti.com]
> Sent: Tuesday, March 23, 2010 5:49 PM
> To: Tony Lindgren
> Cc: Pais, Allen; linux-arm-kernel at lists.infradead.org; linux-
> omap at vger.kernel.org; Pandita, Vikram; Madhusudhan Chikkature Rajashekar
> Subject: mmc errors (was Re: [PATCH] arm: Fix DEBUG_LL for omap zoom2/3)
> 
> Tony Lindgren had written, on 03/23/2010 10:27 AM, the following:
> [...]
> > Then at least one issue remains for zoom3 to be usable..
> > I'm getting tons of MMC errors trying to mount root on it:
> >
> > mmcblk1: error -110 transferring data, sector 2097024, nr 8, card status
> 0x900
> > end_request: I/O error, dev mmcblk1, sector 2097024
> > ...
> >
> I have seen this on few platforms and seem to be related to eMMC usage.
> 
> > Any ideas if that's fixed somewhere also?
> Madhu, any comments?
> 
> --
> Regards,
> Nishanth Menon

  reply	other threads:[~2010-03-24 15:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20  0:36 [PATCH] arm: Fix DEBUG_LL for omap zoom2/3 Tony Lindgren
2010-03-20  0:47 ` Tony Lindgren
2010-03-20  2:48   ` Tony Lindgren
2010-03-20  3:02     ` Tony Lindgren
2010-03-20 23:00       ` Pandita, Vikram
2010-03-23  0:09         ` Tony Lindgren
2010-03-22  7:18     ` Pais, Allen
2010-03-22 21:20       ` Tony Lindgren
2010-03-23  1:25         ` Tony Lindgren
2010-03-23  5:46         ` Pais, Allen
2010-03-23 15:27           ` Tony Lindgren
2010-03-23 22:49             ` mmc errors (was Re: [PATCH] arm: Fix DEBUG_LL for omap zoom2/3) Nishanth Menon
2010-03-24 15:31               ` Madhusudhan [this message]
2010-03-24 15:32               ` Madhusudhan
2010-03-24 15:35               ` Madhusudhan
2010-03-24 15:52                 ` Laurent Epinat
2010-03-30 23:35             ` [PATCH] arm: Fix DEBUG_LL for omap zoom2/3 Madhusudhan
2010-03-31  6:11               ` G, Manjunath Kondaiah
2010-03-31 16:46                 ` Madhusudhan
2010-04-06 16:51             ` Aguirre, Sergio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001cacb67$0687bef0$544ff780@am.dhcp.ti.com' \
    --to=madhu.cr@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).