On Wed, Jul 15, 1998 at 11:00:47AM +0200, Honza Pazdziora wrote:
> Yes, I'll try to create the page. Basically R4400, R4600, R5000,
> PC and SC, anyrate are OK? How about R4000? Other hardware: XGE, XZ
> (for consoles), 10BaseT, any reasonable SCSI? How about the Challenge S?
10BaseT - never tested. I use 10Base2 but I assume the mediaselection works
XGE, XZ graphics are not supported yet. We might however try to use the
ARC firmware to support anything that we don't support yet as a console.
We only support the the builtin WD33C93 hostadapter. Extra GIO boards,
especially the WD33C95 (afaik available in the Challenge S), are not
Challenge S isn't supported yet.
The cache issues seems to be confusing to many people, so here a simple
explanation of the issue. The actual issues are a bit more complex
especially in the case of R4000SC, R4000MC, R4400SC, R4400MC.
Processor types: R4000PC / R4400PC, R4600, R5000. We've got support for
the second level cache as available on the R4600 and R5000 CPU _boards_,
known as R4600SC and R5000SC. We do not support the CPU controlled
cache as in R4000SC, R4400SC and R5000.
Why does the second level cache make a difference? The second level
cache on MIPS systems is ``visible'' to software and the kernel needs
appropriate support for each of them. We do have this support code for
the external cache controllers on the Indy R4600 and R5000 modules.
R4000SC, R4000MC, R4400SC, R4400MC have integrated cache controllers
which we don't support. The R5000 also has one which we don't support.
However the Indy R5000SC modules use an external cache controller and
that one is supported.
There are more MIPS CPU types that we support - some of them even
don't exist yet as silicon - but these types were never shipped in Indys.