From: Quinn Jensen <jensenq@Lineo.COM>
To: linux-mips@oss.sgi.com
Subject: CONFIG_MIPS_UNCACHED
Date: Tue, 23 Jan 2001 16:26:35 -0700 [thread overview]
Message-ID: <3A6E132B.9000103@Lineo.COM> (raw)
Ralf,
On some machines with weird firmware (e.g. IDT 334 board)
the processor comes up with the cache already enabled for
kseg0. In this case, the set_cp0_config() call in mips32.c
to turn off the cache (gated by CONFIG_MIPS_UNCACHED) should
probably come after the first call to flush_cache_all(),
which is safer but still not totally safe, I suppose.
Or am I totally hosed trying to turn the kseg0 cache off
after it was once on?
Quinn Jensen
next reply other threads:[~2001-01-23 23:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 23:26 Quinn Jensen [this message]
2001-01-23 23:53 ` CONFIG_MIPS_UNCACHED Pete Popov
2001-01-24 20:10 ` CONFIG_MIPS_UNCACHED Jun Sun
2001-01-25 0:31 ` CONFIG_MIPS_UNCACHED Ralf Baechle
2001-01-25 1:09 ` CONFIG_MIPS_UNCACHED Pete Popov
2001-01-25 1:37 ` CONFIG_MIPS_UNCACHED Jun Sun
2001-01-26 10:02 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-01-26 10:02 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
-- strict thread matches above, loose matches on Subject: below --
2001-06-23 16:05 CONFIG_MIPS_UNCACHED Jun Sun
2001-06-23 17:17 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-23 17:17 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-23 17:49 ` CONFIG_MIPS_UNCACHED Jun Sun
2001-06-23 20:15 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-23 20:15 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-25 4:42 ` CONFIG_MIPS_UNCACHED Jun Sun
2001-06-25 6:51 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-25 6:51 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-25 16:38 ` CONFIG_MIPS_UNCACHED Jun Sun
2001-06-25 17:35 ` CONFIG_MIPS_UNCACHED Justin Carlson
2001-06-26 8:50 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-26 8:50 ` CONFIG_MIPS_UNCACHED Kevin D. Kissell
2001-06-26 13:11 ` CONFIG_MIPS_UNCACHED Maciej W. Rozycki
2001-06-25 13:22 ` CONFIG_MIPS_UNCACHED Maciej W. Rozycki
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=3A6E132B.9000103@Lineo.COM \
--to=jensenq@lineo.com \
--cc=linux-mips@oss.sgi.com \
/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