From: Pete Popov <ppopov@mvista.com>
To: linux-mips <linux-mips@oss.sgi.com>
Subject: rm7k
Date: 26 Oct 2001 15:00:53 -0700 [thread overview]
Message-ID: <1004133653.7556.11.camel@zeus> (raw)
Ralf,
tlb-r4k.c is used for the rm7k, but this piece in probe_tlb() fails:
if (!(config & (1 << 31)))
/*
* Not a MIPS32 complianant CPU. Config 1 register not
* supported, we assume R4k style. Cpu probing already figured
* out the number of tlb entries.
*/
return;
Bit 31 on the rm7k indicates whether or not scache is present. If scache
is not present (disabled), the above test passes and we end up reading
config1, which doesn't exist, so we setup the tlbsize to a bogus value.
Pete
reply other threads:[~2001-10-26 21:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1004133653.7556.11.camel@zeus \
--to=ppopov@mvista.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