From: Gary Thomas <gary@mlbassoc•com>
To: Linux PPC Development <linuxppc-dev@ozlabs•org>
Subject: Re: MMC on MPC8379
Date: Thu, 03 Feb 2011 11:48:01 -0700 [thread overview]
Message-ID: <4D4AF861.2050605@mlbassoc.com> (raw)
In-Reply-To: <4D4717AD.2040905@mlbassoc.com>
On 01/31/2011 01:12 PM, Gary Thomas wrote:
> I'm running 2.6.32 on MPC8379, trying to use the SDHCI interface.
> It seems to work, reads are fine, but when I write to the device
> (I've tried both eMMC soldered-on and pluggable MMC/SD cards),
> I get intermittent failures. Specifically, some blocks will be
> written while others fail. I haven't yet found a pattern.
>
> Is there anything special about this interface? I notice that
> it's not really used by any FSL platforms although the driver
> claims support.
On the surface, it looks like it should work and I'm perplexed
by the failures.
Does anyone have any ideas or experience with this device?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2011-02-03 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 20:12 MMC on MPC8379 Gary Thomas
2011-02-03 18:48 ` Gary Thomas [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=4D4AF861.2050605@mlbassoc.com \
--to=gary@mlbassoc$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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