From: Kenneth Johansson <kenneth@southpole.se>
To: u-boot-users <u-boot-users@lists.sourceforge.net>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: mpc5121 cache coherency
Date: Wed, 18 Jun 2008 21:29:51 +0200 [thread overview]
Message-ID: <1213817391.27790.27.camel@localhost.localdomain> (raw)
I have tried to speed up u-boot by turning on I/D cache during boot.
It sort of works and gives quite a boost but I'm having problems with
the ethernet driver that no longer works.
What I'm seeing is that the cpu do not notice the ethernet hardwares
updates that is located in DRAM. Basically what is expected from a cache
incoherent system.
Now my question is should not the e300 core detect writes to the DRAM
and reload the cached data ??
---
To get cache working I'm turning on the MMU and program some BAT
registers to a 1-1 mapping where only DRAM has cache on and all other
memory regions like the IMMR, flash ... has cache off.
next reply other threads:[~2008-06-18 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 19:29 Kenneth Johansson [this message]
2008-06-18 19:38 ` [U-Boot-Users] mpc5121 cache coherency John Rigby
2008-06-18 21:16 ` kenneth johansson
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=1213817391.27790.27.camel@localhost.localdomain \
--to=kenneth@southpole.se \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=u-boot-users@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).