From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][MMC] Buggy cards need to leave programming state
Date: Mon, 26 Dec 2005 20:17:37 +0000 [thread overview]
Message-ID: <20051226201737.GB17191@flint.arm.linux.org.uk> (raw)
In-Reply-To: <43B04B43.5080705@drzeus.cx>
On Mon, Dec 26, 2005 at 08:57:55PM +0100, Pierre Ossman wrote:
> Russell King wrote:
> > whereas it's impossible to tell with the November dump because
> > the useful information has been edited out. Hence the November
> > dump is rather useless.
>
> What seems to be missing?
The lines containing the respose to the CMD0x18 and CMD0x0d - iow
the card status. I'd like to see the result from the previous
two commands to the errors occurring.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-12-26 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 13:19 [RFC][MMC] Buggy cards need to leave programming state Pierre Ossman
2005-12-26 19:13 ` Russell King
2005-12-26 19:57 ` Pierre Ossman
2005-12-26 20:17 ` Russell King [this message]
2005-12-26 20:33 ` Pierre Ossman
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=20051226201737.GB17191@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--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