From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] i.MX51: FEC: Cache coherency problem?
Date: Tue, 19 Jul 2011 10:21:12 +0200 [thread overview]
Message-ID: <4E253E78.4050801@aribaud.net> (raw)
In-Reply-To: <20110719094406.686e2a45@archvile>
Hi David,
Le 19/07/2011 09:44, David Jander a ?crit :
>
> Hi Stefano,
>
> On Mon, 18 Jul 2011 18:55:05 +0200
> Stefano Babic<sbabic@denx.de> wrote:
>
>> On 07/18/2011 05:18 PM, David Jander wrote:
>>>
>>> Hi all,
>>
>> Hi David,
>>
>>> What is going on here? Why did this work with caches enabled before??
>>
>> I think cache was always disabled..
>
> I had even L2-caches enabled in u-boot (copied/adapted some code from OMAP
> cache.S), and called i/dcache_enable() from board code like this:
>
> int board_late_init(void)
> {
> power_init();
> probe_board_type();
> icache_enable();
> dcache_enable();
>
> return 0;
> }
>
> Is there a reason this wouldn't have worked before?
>
> Suppose it didn't. Does that mean we need to use the MMU to properly mark
> regions of register space and specially FEC BD's as not-cached? Or do we need
> to flash caches manually each time such a memory region is accessed?
> I am kind of a CPU-speed-junkie, so I am not sure I want to live without
> caches enabled in u-boot ;-)
You would have to flush (before sending packets / starting external
memory-to-device DMA) and invalidate (before reading received packets /
after external device-to-memory DMA is done); using MMU and mapping
cached/non-cached areas is IMO overkill, and will hurt CPU accesses to
the xmit/receive buffers and descriptors.
> Best regards,
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-07-19 8:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 15:18 [U-Boot] i.MX51: FEC: Cache coherency problem? David Jander
2011-07-18 16:16 ` Aneesh V
2011-07-19 7:26 ` David Jander
2011-07-19 11:07 ` Matthias Weißer
2011-07-19 11:17 ` David Jander
2011-07-19 11:20 ` Wolfgang Denk
2011-07-19 12:10 ` David Jander
2011-07-20 6:29 ` David Jander
2011-07-20 8:56 ` Albert ARIBAUD
2011-07-20 9:21 ` David Jander
2011-07-20 10:29 ` Aneesh V
2011-07-20 11:31 ` David Jander
2011-07-20 12:05 ` Aneesh V
2011-07-19 11:19 ` Wolfgang Denk
2011-07-19 14:31 ` Matthias Weißer
2011-07-19 11:51 ` Aneesh V
2011-07-18 16:55 ` Stefano Babic
2011-07-19 7:44 ` David Jander
2011-07-19 8:21 ` Albert ARIBAUD [this message]
2011-07-19 8:37 ` David Jander
2011-07-19 8:43 ` Aneesh V
2011-07-19 8:58 ` David Jander
2011-07-19 9:11 ` Albert ARIBAUD
2011-07-19 11:50 ` Aneesh V
2011-07-19 11:42 ` Aneesh V
2011-07-19 9:05 ` Albert ARIBAUD
2011-07-19 14:36 ` J. William Campbell
2011-07-19 15:17 ` David Jander
2011-07-19 18:14 ` Anton Staaf
2011-07-19 20:11 ` J. William Campbell
2011-07-20 13:02 ` Albert ARIBAUD
[not found] ` <4E26DF9D.5070709@comcast.net>
[not found] ` <4E26E7AA.9070001@aribaud.net>
2011-07-20 15:36 ` J. William Campbell
2011-07-21 6:48 ` David Jander
2011-07-23 13:04 ` Albert ARIBAUD
2011-07-23 15:35 ` J. William Campbell
2011-07-20 8:37 ` Aneesh V
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=4E253E78.4050801@aribaud.net \
--to=albert.u.boot@aribaud.net \
--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 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.