From: Roopesh <roopesh@cyberspace.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Roopesh <roopesh@cyberspace.org>, linux-kernel@vger.kernel.org
Subject: Re: MMC/SD: Write operation in invalid states by borken cards.
Date: Fri, 23 Nov 2007 05:27:27 -0500 [thread overview]
Message-ID: <20071123102727.GA4804@grex.cyberspace.org> (raw)
In-Reply-To: <20071110115119.7944db28@poseidon.drzeus.cx>
:---------- Original Message ----------
:
:From: Pierre Ossman [drzeus-list@drzeus.cx]
:To : To Roopesh
:Sub : Re: MMC/SD: Write operation in invalid states by borken cards.
:Sent: Sat, Nov 10, 2007 at 05:51:19AM EST
: On Thu, 8 Nov 2007 03:24:10 -0500
: Roopesh <roopesh@cyberspace.org> wrote:
:
: > Hi,
: >
: > If a write operation fails, shouldnt we still check for the card
: > state to be 'ready to accept next data'?
: >
: > This question is because I have noticed that some (broken) cards
: > fail the write command, and the immediately issued subsequent
: > commands also fail since the card state was never checked before
: > sending these commands.
: > (There was a discussion about these cards at the thread: "MMC:
: > CRC Errors with 2GB cards)
: >
:
: I'm confused. Didn't the previous fix solve your problems?
I am sorry I couldnt respond in time, and also for creating the
confusion. The previous fix did solve my problem. However, if
for some other reason the card goes into an invalid state and a
write command fails, shouldnt we still check for the card state
before sending the next IO command?
: Rgds
: --
: -- Pierre Ossman
:
: Linux kernel, MMC maintainer http://www.kernel.org
: PulseAudio, core developer http://pulseaudio.org
: rdesktop, core developer http://www.rdesktop.org
prev parent reply other threads:[~2007-11-23 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 8:24 Roopesh
2007-11-10 10:51 ` Pierre Ossman
2007-11-23 10:27 ` Roopesh [this message]
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=20071123102727.GA4804@grex.cyberspace.org \
--to=roopesh@cyberspace.org \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®