From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: Jarkko Lavinen <jarkko.lavinen@nokia.com>
Cc: "philipl@overt.org" <philipl@overt.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18 RFC] mmc: Add support for mmc v4 wide-bus modes
Date: Tue, 24 Oct 2006 21:11:45 +0200 [thread overview]
Message-ID: <453E6571.4080504@drzeus.cx> (raw)
In-Reply-To: <20061016120839.GA16127@angel.research.nokia.com>
Jarkko Lavinen wrote:
> Hi Philip and Pierre
>
> On Sat, Oct 14, 2006 at 03:15:08PM -0400, philipl@overt.org wrote:
>> I keep getting a data CRC error back - for both the reads and writes.
>
> The spec says these can be ignored, both reads and writes. The
> card ignores optional CRC16 when sending data and likewise host
> ignores optional CRC when reading back.
If this is the case, then we cannot support it the way the MMC layer is
built right now. A CRC error means the data is bad and might not even be
in the buffer.
To be honest, many controllers will probably not even transfer the data
to the CPU, so we can't just ignore the CRC error. So for now, I guess
this will have to be an unsupported feature.
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:[~2006-10-24 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 19:15 [PATCH 2.6.18 RFC] mmc: Add support for mmc v4 wide-bus modes philipl
2006-10-15 19:44 ` Pierre Ossman
2006-10-16 12:08 ` Jarkko Lavinen
2006-10-24 19:11 ` Pierre Ossman [this message]
2006-10-24 19:05 ` Pierre Ossman
2006-10-25 5:29 ` philipl
2006-10-29 9:16 ` 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=453E6571.4080504@drzeus.cx \
--to=drzeus-mmc@drzeus.cx \
--cc=jarkko.lavinen@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philipl@overt.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