From: Dirk Behme <dirk.behme@de.bosch.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] i.MX: fsl_esdhc: allow use with cache enabled.
Date: Fri, 20 Jul 2012 07:35:30 +0200 [thread overview]
Message-ID: <5008EE22.6040003@de.bosch.com> (raw)
In-Reply-To: <201207200432.46649.marex@denx.de>
On 20.07.2012 04:32, Marek Vasut wrote:
> Dear Dirk Behme,
>
> [...]
>
>>>> I'm not likely to have any time until after FTF next week.
>>>>
>>>> Any chance that a PPC maintainer can chime in here?
>>> I think WD applied the cache stub patch already. Can you try now please?
>> Ping ;)
>>
>> Thanks
>>
>> Dirk
>
> I just noticed this with latest mainline:
> Configuring for MPC8569MDS_ATM - Board: MPC8569MDS, Options: ATM
> make: *** [u-boot] Error 1
> powerpc-linux-size: './u-boot': No such file
> drivers/mmc/libmmc.o: In function `esdhc_setup_data':
> /home/marex/testing/u-boot.git/drivers/mmc/fsl_esdhc.c:193: undefined reference
> to `flush_dcache_range'
> drivers/mmc/libmmc.o: In function `check_and_invalidate_dcache_range':
> /home/marex/testing/u-boot.git/drivers/mmc/fsl_esdhc.c:263: undefined reference
> to `invalidate_dcache_range'
> make: *** [u-boot] Error 1
> Configuring for MPC8569MDS_NAND - Board: MPC8569MDS, Options: NAND
> make: *** [u-boot] Error 1
> powerpc-linux-size: './u-boot': No such file
> drivers/mmc/libmmc.o: In function `esdhc_setup_data':
> /home/marex/testing/u-boot.git/drivers/mmc/fsl_esdhc.c:193: undefined reference
> to `flush_dcache_range'
> drivers/mmc/libmmc.o: In function `check_and_invalidate_dcache_range':
> /home/marex/testing/u-boot.git/drivers/mmc/fsl_esdhc.c:263: undefined reference
> to `invalidate_dcache_range'
> make: *** [u-boot] Error 1
>
> Can this be caused by this patch?
Yes, I think so.
Reading the logs, to my understanding the conclusion in
http://lists.denx.de/pipermail/u-boot/2012-May/124036.html
was to "add an empty flush_dcache_range() to the MPC85xx, maybe as weak
function".
Then
http://lists.denx.de/pipermail/u-boot/2012-June/126097.html
mentions "WD applied the cache stub patch already".
So do we have this "cache stub patch" somewhere which fixes the issue
mentioned above? I'm not sure I've seen it ...
Best regards
Dirk
next prev parent reply other threads:[~2012-07-20 5:35 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
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 [this message]
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=5008EE22.6040003@de.bosch.com \
--to=dirk.behme@de.bosch.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