From: Dan Malek <dan@embeddededge.com>
To: Matt Porter <porter@cox.net>
Cc: Jean-Denis Boyer <jdboyer@mediatrix.com>,
kas turi <inox_kas@yahoo.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Disabling data cache
Date: Wed, 02 Apr 2003 14:23:01 -0500 [thread overview]
Message-ID: <3E8B3895.5050908@embeddededge.com> (raw)
In-Reply-To: 20030402094037.A31751@home.com
Matt Porter wrote:
> On Wed, Apr 02, 2003 at 09:28:21AM -0500, Jean-Denis Boyer wrote:
>
>>There is a kernel configuration option for that: CONFIG_DCACHE_DISABLE.
>>In the kernel configuration UI, look into the section 'MPC8260 CPM Options'.
>
>
> There is no code backing that option in linuxppc_2_4_devel, it is useless.
It was orginally done for 8xx processors. I suspect someone (I don't
think it was me) :-) tried to consolidate 8xx and 82xx CPM configurations
and messed it up.
> Certainly one could take what one person did (in the old post I referenced)
> and put it under a config option for debug purposes. Yet another nice
> project for somebody. :)
Data cache configuration options are a PITA for most processors. You would
have to litter #ifdefs all over the kernel. IMHO, you should make cache
coherent busses work correctly, then write code. In the case of 8xx, it is
a trival bit setting in one control register that can be done at start up
time, making debug easier for this non-coherent cache processor.
This #ifdef used to be near the end of initial_mmu() in head_8xx.S. When
I added the TLB Pinning option, I decided to simplify the code and remove
the disable data cache option. If necessary, it is easy to do this with
a simple code change. The copyback #ifdef is a little more useful as we
are more likely to see memory controller set up rather than data cache
coherency problems these days and this option can help debug those.
I'll remove the configuration option.
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-02 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 14:28 Disabling data cache Jean-Denis Boyer
2003-04-02 16:40 ` Matt Porter
2003-04-02 19:23 ` Dan Malek [this message]
2003-04-02 19:46 ` Tom Rini
2003-04-02 20:19 ` Wolfgang Denk
2003-04-03 14:59 ` Tom Rini
2003-04-04 22:49 ` Wolfgang Denk
2003-04-02 21:59 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2003-04-02 17:14 Ralph Blach
2003-04-02 1:34 kas turi
2003-04-02 5:30 ` Matt Porter
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=3E8B3895.5050908@embeddededge.com \
--to=dan@embeddededge.com \
--cc=inox_kas@yahoo.com \
--cc=jdboyer@mediatrix.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=porter@cox.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).