From: Dominic Sweetman <dom@algor.co.uk>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com, nigel@algor.co.uk
Subject: Re: R5000 support (specifically two-way set-associative cache...)
Date: Tue, 20 Jun 2000 10:47:42 +0100 (BST) [thread overview]
Message-ID: <200006200947.KAA08574@mudchute.algor.co.uk> (raw)
In-Reply-To: <394EA5A0.B882F66A@mvista.com>
Jun Sun (jsun@mvista.com) writes:
> 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?
The two-way cache on the R5000 (and its R4600 parent) is implemented
so that the cache operations used during running don't have to know
about the cache organisation. Even initialisation of an R5000 cache
can be done by a piece of code which has no reference to two-wayness
and just works over R4x00/R5000 CPUs.
So this is not *necessarily* a problem.
> 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?
A note on this and Geert's response: early Vrc5074 system controller
chips had lots of bugs, with some particularly nasty ones hitting PCI
transfers with external initiators (like the ethernet chip). Anyone
pioneering Linux on it should check carefully with NEC about the
status of their particular revision.
Dominic Sweetman
Algorithmics Ltd
dom@algor.co.uk
next prev parent reply other threads:[~2000-06-20 9:48 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
2000-06-20 8:44 ` Geert Uytterhoeven
2000-06-20 9:47 ` Dominic Sweetman [this message]
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=200006200947.KAA08574@mudchute.algor.co.uk \
--to=dom@algor.co.uk \
--cc=jsun@mvista.com \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.com \
--cc=nigel@algor.co.uk \
/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