From: eric@eukrea.com (Eric Bénard)
To: linux-arm-kernel@lists.infradead.org
Subject: [MX25][MMC] mmc esdhc failure in 3.3
Date: Tue, 27 Mar 2012 10:12:59 +0200 [thread overview]
Message-ID: <20120327101259.73525f9d@eb-e6520> (raw)
In-Reply-To: <85b807b77d73328485781d6fa1568e46@mail.fqingenieria.es>
Hi,
Le Tue, 27 Mar 2012 09:32:36 +0200,
joancarles <joancarles@fqingenieria.es> a ?crit :
> G'day
>
> This is still present, and we have absolutely no idea where to continue
> searching for the solution of the problem. Any pointers? Any git trees
> of mmc driver changes we could try? Anybody else with a MX25 that has
> this issue?
>
does that attached patch fix your problem ?
Eric
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-esdhc-imx-unbreak-on-i.MX25.patch
Type: text/x-patch
Size: 1054 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120327/6729fea5/attachment.bin>
next prev parent reply other threads:[~2012-03-27 8:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5e57eb999780335721212bb8d411406f@mail.fqingenieria.es>
2012-03-12 13:12 ` [MX25][MMC] mmc esdhc failure in 3.3-rc5 (still present in rc7) joancarles
[not found] ` <20120312132423.GC2459@pengutronix.de>
[not found] ` <9018463dfcd3c9e9a311aeed42b758bf@mail.fqingenieria.es>
[not found] ` <0E83723C55F66F43A6041464FE31119D099A34@039-SN2MPN1-011.039d.mgd.msft.net>
[not found] ` <a06e68c3687c7390e15950bc20831fd4@mail.fqingenieria.es>
2012-03-27 7:32 ` [MX25][MMC] mmc esdhc failure in 3.3 joancarles
2012-03-27 7:59 ` joancarles
2012-03-27 8:12 ` Eric Bénard [this message]
2012-03-27 8:46 ` joancarles
2012-03-27 8:58 ` Eric Bénard
2012-03-27 13:03 ` Zhu Richard-R65037
2012-03-27 9:01 ` Wolfram Sang
2012-03-27 9:06 ` Eric Bénard
2012-03-27 9:14 ` Wolfram Sang
2012-03-27 9:23 ` Eric Bénard
2012-03-27 9:36 ` Wolfram Sang
2012-03-27 9:33 ` joancarles
2012-03-27 9:40 ` Eric Bénard
2012-03-27 10:56 ` joancarles
2012-03-28 9:26 ` joancarles
2012-03-28 14:01 ` joancarles
2012-03-27 9:45 ` Wolfram Sang
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=20120327101259.73525f9d@eb-e6520 \
--to=eric@eukrea.com \
--cc=linux-arm-kernel@lists.infradead.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