From: Wolfram Sang <w.sang@pengutronix.de>
To: joancarles <joancarles@fqingenieria.es>
Cc: linux-mmc@vger.kernel.org, shawn.guo@linaro.org,
Hong-Xing.Zhu@freescale.com
Subject: Re: [MX25][MMC] mmc esdhc failure in 3.3-rc5
Date: Mon, 12 Mar 2012 22:45:45 +0100 [thread overview]
Message-ID: <20120312214545.GC28087@pengutronix.de> (raw)
In-Reply-To: <9018463dfcd3c9e9a311aeed42b758bf@mail.fqingenieria.es>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On Mon, Mar 12, 2012 at 03:50:03PM +0100, joancarles wrote:
> >>What could have changed between 2.6.39.3 and 3.3-rc5 to trigger this
> >>behaviour? A quick look at
> >>
> >>git diff v2.6.39 drivers/mmc/host/sdhci-esdhc-imx.c
> >
> >I'd recommend:
> >
> >git log v2.6.39.. drivers/mmc/host/sdhci-esdhc-imx.c
>
> I have been staring at those commits, however with very little
> domain knowledge it's a shot in the dark.
Have you tried copying sdhci-esdhc-imx.c from 2.6.39 to the current kernel
(might need some build fixes)? If that doesn't work, there might be something
wrong in the sdhci-driver itself, and not the esdhc-extension.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-03-12 21:45 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 11:29 [MX25][MMC] mmc esdhc failure in 3.3-rc5 joancarles
2012-03-12 13:12 ` [MX25][MMC] mmc esdhc failure in 3.3-rc5 (still present in rc7) joancarles
2012-03-12 13:12 ` joancarles
2012-03-12 13:24 ` [MX25][MMC] mmc esdhc failure in 3.3-rc5 Wolfram Sang
2012-03-12 14:50 ` joancarles
2012-03-12 21:45 ` Wolfram Sang [this message]
2012-03-13 11:20 ` joancarles
2012-03-13 5:55 ` Zhu Richard-R65037
2012-03-16 15:03 ` joancarles
2012-03-27 7:32 ` [MX25][MMC] mmc esdhc failure in 3.3 joancarles
2012-03-27 7:32 ` joancarles
2012-03-27 7:59 ` joancarles
2012-03-27 7:59 ` joancarles
2012-03-27 8:12 ` Eric Bénard
2012-03-27 8:12 ` Eric Bénard
2012-03-27 8:46 ` joancarles
2012-03-27 8:46 ` joancarles
2012-03-27 8:58 ` Eric Bénard
2012-03-27 8:58 ` Eric Bénard
2012-03-27 13:03 ` Zhu Richard-R65037
2012-03-27 13:03 ` Zhu Richard-R65037
2012-03-27 9:01 ` Wolfram Sang
2012-03-27 9:01 ` Wolfram Sang
2012-03-27 9:06 ` Eric Bénard
2012-03-27 9:06 ` Eric Bénard
2012-03-27 9:14 ` Wolfram Sang
2012-03-27 9:14 ` Wolfram Sang
2012-03-27 9:23 ` Eric Bénard
2012-03-27 9:23 ` Eric Bénard
2012-03-27 9:36 ` Wolfram Sang
2012-03-27 9:36 ` Wolfram Sang
2012-03-27 9:33 ` joancarles
2012-03-27 9:33 ` joancarles
2012-03-27 9:40 ` Eric Bénard
2012-03-27 9:40 ` Eric Bénard
2012-03-27 10:56 ` joancarles
2012-03-27 10:56 ` joancarles
2012-03-28 9:26 ` joancarles
2012-03-28 9:26 ` joancarles
2012-03-28 14:01 ` joancarles
2012-03-28 14:01 ` joancarles
2012-03-27 9:45 ` Wolfram Sang
2012-03-27 9:45 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2012-02-29 12:55 [MX25][MMC] mmc esdhc failure in 3.3-rc5 joancarles at fqingenieria.es
2012-02-29 14:21 ` Baruch Siach
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=20120312214545.GC28087@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=Hong-Xing.Zhu@freescale.com \
--cc=joancarles@fqingenieria.es \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.guo@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.