From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] i.MX: fsl_esdhc: allow use with cache enabled.
Date: Tue, 15 May 2012 16:01:48 -0700 [thread overview]
Message-ID: <4FB2E05C.6070304@boundarydevices.com> (raw)
In-Reply-To: <20120515150933.7f642e77@wker>
On 05/15/2012 06:09 AM, Anatolij Gustschin wrote:
> Hi Dirk,
>
> On Tue, 15 May 2012 14:58:54 +0200
> Dirk Behme<dirk.behme@de.bosch.com> wrote:
>
>> On 09.05.2012 07:45, Stefano Babic wrote:
> ...
>>> The problem with an #ifdef is that it is not very generic - we should
>>> add some #if (defined(CONFIG_MX51) || defined(CONFIG_MX53) || ...
>>> and update the driver for each new SOCs. I think also that maybe the
>>> best way is to add an empty flush_dcache_range() to the MPC85xx, maybe
>>> as weak function.
>>
>> You might have noticed that I'm looking through my list of open patches.
>> So: Any news regarding V3 of this patch? ;)
>
> Stefano is on vacation; please don't expect any quick reply from him.
>
Vacation? Is that one of those European words I should really know? ;)
I don't have the same excuse. I'm just struggling to find a few hours
to take a stab at this.
I'm without a PPC device and compiler, so I'll need some assistance in
validating things.
Regards,
Eric
next prev parent reply other threads:[~2012-05-15 23:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <http://lists.denx.de/pipermail/u-boot/2012-March/#119312>
2012-04-26 0:28 ` [U-Boot] [PATCH V2] i.MX: fsl_esdhc: allow use with cache enabled Eric Nelson
2012-05-08 22:59 ` Andy Fleming
2012-05-08 23:31 ` Eric Nelson
2012-05-09 5:45 ` Stefano Babic
2012-05-15 12:58 ` Dirk Behme
2012-05-15 13:09 ` Anatolij Gustschin
2012-05-15 23:01 ` Eric Nelson [this message]
2012-05-15 23:35 ` Marek Vasut
2012-06-12 17:07 ` Stefano Babic
2012-06-12 17:14 ` Eric Nelson
2012-06-12 17:23 ` Marek Vasut
2012-07-11 6:29 ` Dirk Behme
2012-07-13 10:37 ` Marek Vasut
2012-07-20 2:32 ` Marek Vasut
2012-07-20 5:35 ` Dirk Behme
2012-07-20 8:53 ` Stefano Babic
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=4FB2E05C.6070304@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=u-boot@lists.denx.de \
/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