From: Ralf Baechle <ralf@oss.sgi.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: R5000 support (specifically two-way set-associative cache...)
Date: Tue, 20 Jun 2000 03:51:59 +0200 [thread overview]
Message-ID: <20000620035158.F28452@bacchus.dhis.org> (raw)
In-Reply-To: <394EA5A0.B882F66A@mvista.com>; from jsun@mvista.com on Mon, Jun 19, 2000 at 03:58:40PM -0700
On Mon, Jun 19, 2000 at 03:58:40PM -0700, Jun Sun wrote:
> I looked into the R5000 support and have a couple of questions:
>
> 1. Is R5000, specifically NEC Vr5000, fully supported? I have seen
> CONFIG_CPU_R5000 defined, but it does not appear to do much.
Indeed, the various CPU options for the R4xxx / R5xxx CPUs mostly deal
with C compiler options as a minor optimization.
> 2. Specifically, NEC Vr5000 has two-way set-associative cache. I
> browsed through the cache code, and got concerned that I don't see any
> code that seems to take care of that. Do I miss something?
Yes :-)
The R5000 has R4600 style caches, so also uses the same code.
> 3. I understand Geert has a port to DDB5074 (with Vr5000 CPU). Is this
> port completed (including all interrupts, PCI related stuff). Is this
> port reliable?
I leave the question to Geert to answer.
Ralf
next prev parent reply other threads:[~2000-06-20 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 22:58 R5000 support (specifically two-way set-associative cache...) Jun Sun
2000-06-20 1:51 ` Ralf Baechle [this message]
2000-06-20 8:44 ` Geert Uytterhoeven
2000-06-20 9:47 ` Dominic Sweetman
2000-06-20 10:02 ` Geert Uytterhoeven
2000-06-20 18:41 ` Jun Sun
2000-06-20 19:01 ` Jun Sun
2000-06-20 20:59 ` Dominic Sweetman
2000-07-01 1:22 ` Jun Sun
-- strict thread matches above, loose matches on Subject: below --
2000-07-01 6:46 Kevin D. Kissell
2000-07-01 6:46 ` Kevin D. Kissell
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=20000620035158.F28452@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=jsun@mvista.com \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.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