From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Roopesh <roopesh@cyberspace.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: MMC: CRC Errors with 2GB cards
Date: Sat, 27 Oct 2007 14:00:17 +0200 [thread overview]
Message-ID: <20071027140017.41e9d67f@poseidon.drzeus.cx> (raw)
In-Reply-To: <20071019161700.GA19254@grex.cyberspace.org>
Hi Roopesh,
I'm terribly sorry I haven't replied sooner. I put your message on my todo list, figuring I could get to it within a day or two, but as you noticed, that didn't quite happen. :/
On Fri, 19 Oct 2007 12:17:00 -0400
Roopesh <roopesh@cyberspace.org> wrote:
> Hi,
>
> I am seeing a lot of CRC errors happening with CMD25 on a couple
> of Transcend 2GB cards (specifiation version 1.1). However, if
> I apply the following patch, I see no errors being reported
>
Ok, so the card is mishandling the state bits a bit. We should be able to work around that.
> @@ -310,8 +311,8 @@
> req->rq_disk->disk_name, err);
> goto cmd_err;
> }
> - } while (!(cmd.resp[0] & R1_READY_FOR_DATA));
> -
> + } while (!(R1_CURRENT_STATE(cmd.resp[0]) == 4));
> +
> #if 0
This might trade us one problem for another. Could you try the following:
} while (!(cmd.resp[0] & R1_READY_FOR_DATA) || (R1_CURRENT_STATE(cmd.resp[0]) == 7));
This should also work for cards that mishandle the state field, and if the card jumps to
some odd state for some reason.
>
> I am just wondering if I have set of broken cards. Any pointers
> in this regard?
>
You do. But don't be too alarmed, that is unfortunately the norm. :/
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2007-10-27 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 16:17 Roopesh
2007-10-27 12:00 ` Pierre Ossman [this message]
2007-10-29 9:50 ` Roopesh
2007-10-31 19:55 ` Pierre Ossman
2007-11-01 10:39 ` Roopesh
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=20071027140017.41e9d67f@poseidon.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roopesh@cyberspace.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
Powered by JetHome