From: Chris Ball <cjb@laptop.org>
To: Philip Rakity <prakity@marvell.com>
Cc: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>,
Kyungmin Park <kmpark@infradead.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"andrew.chih.howe.khor@intel.com"
<andrew.chih.howe.khor@intel.com>,
"kok.howg.ewe@intel.com" <kok.howg.ewe@intel.com>
Subject: Re: A MMC card transfer issue
Date: Wed, 19 Jan 2011 17:42:33 +0000 [thread overview]
Message-ID: <20110119174233.GA30494@void.printf.net> (raw)
In-Reply-To: <4C4E7DE5-7CF1-4D97-9CAD-F600FCBE477A@marvell.com>
Hi,
On Tue, Jan 18, 2011 at 10:05:04PM -0800, Philip Rakity wrote:
>
> For 1 bit transcend cards you need these 2 patches.
>
> >From 22113efd00491310da802f3b1a9a66cfcf415fac Mon Sep 17 00:00:00 2001
> From: Aries Lee <arieslee@jmicron.com>
> Date: Wed, 15 Dec 2010 08:14:24 +0100
> Subject: [PATCH] mmc: Test bus-width for old MMC devices
Present in 2.6.38-rc1.
> >From 08c82dfad2458f8f9b83126224a85e7ea9e2b046 Mon Sep 17 00:00:00 2001
> From: Takashi Iwai <tiwai@suse.de>
> Date: Wed, 22 Dec 2010 09:59:44 +0100
> Subject: [PATCH] mmc: fix mmc_set_bus_width_ddr() call without bus-width-test cap
Also present in 2.6.38-rc1.
So, please re-test against 2.6.38-rc1 and let us know whether you still
have problems. Thanks,
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-01-19 17:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 5:39 A MMC card transfer issue Tomoya MORINAGA
2010-11-09 5:53 ` Kyungmin Park
2010-11-09 7:29 ` Tomoya MORINAGA
2010-11-11 2:59 ` Tomoya MORINAGA
2010-12-01 1:08 ` Tomoya MORINAGA
[not found] ` <2D50F985-2383-4406-8514-DFE462A5F546@marvell.com>
[not found] ` <4D2E0464ABB54FFF9C10583336E27879@hacdom.okisemi.com>
2011-01-19 0:59 ` Philip Rakity
2011-01-19 1:29 ` Tomoya MORINAGA
2011-01-19 1:41 ` Chris Ball
2011-01-19 3:12 ` Philip Rakity
2011-01-19 6:05 ` Philip Rakity
2011-01-19 6:30 ` Tomoya MORINAGA
2011-01-19 17:42 ` Chris Ball [this message]
2011-01-19 23:49 ` Tomoya MORINAGA
2011-01-26 8:28 ` Tomoya MORINAGA
2011-01-26 15:42 ` Philip Rakity
2011-01-27 1:00 ` Tomoya MORINAGA
2011-01-27 1:03 ` Philip Rakity
2011-01-27 1:31 ` Tomoya MORINAGA
2011-01-27 1:43 ` Philip Rakity
2011-01-27 3:20 ` Tomoya MORINAGA
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=20110119174233.GA30494@void.printf.net \
--to=cjb@laptop.org \
--cc=andrew.chih.howe.khor@intel.com \
--cc=kmpark@infradead.org \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=prakity@marvell.com \
--cc=tomoya-linux@dsn.okisemi.com \
/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