From: Kumba <kumba@gentoo.org>
To: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
Cc: linux-mips@linux-mips.org
Subject: Re: R1000 status
Date: Sat, 19 May 2007 15:00:15 -0400 [thread overview]
Message-ID: <464F493F.7090405@gentoo.org> (raw)
In-Reply-To: <49027.193.253.35.188.1179557496.squirrel@eppesuigoccas.homedns.org>
Giuseppe Sacco wrote:
> Hi all,
> reading many web pages I think to understand that R10000 is supported on
> IP22 systems and is unsupported on IP32 systems because of its cache.
>
> The page http://www.linux-mips.org/wiki/Silicon_Graphics display a
> different result: R10000 on SIGG O2 is supported.
>
> Is there any news or a list of known problems?
R10000 on IP22 actually refers to the IP28 system, Indigo2 R10000 Impact. And
it does work if you use the latest patches, but YMMV.
R10000 on IP32 is a different story. I used to maintain a patch that was
essentially the IP28 patch minus IP28-specific bits to the kernel, and built
with an R10K-equipped gcc toolchain, produced a kernel that would run for a
decent amount of time, however, using the scsi disk or the network module could
lock the machine up. You also got a gazillion CRIME CPU errors on the main console.
I'll have to rebuild the patch again and see how it handles nowadays, but I
believe that, regardless, enhancements need to be made to aic7xxx to protect
against the non-cache cohenecy of the machine, and something equivalent to the
meth module (network) as well. That, or someone implements the "Juice"
capability of the system.
--Kumba
--
Gentoo/MIPS Team Lead
"Such is oft the course of deeds that move the wheels of the world: small hands
do them because they must, while the eyes of the great are elsewhere." --Elrond
prev parent reply other threads:[~2007-05-19 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 6:51 R1000 status Giuseppe Sacco
2007-05-19 7:33 ` peter fuerst
2007-05-19 19:01 ` Kumba
2007-05-19 19:00 ` Kumba [this message]
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=464F493F.7090405@gentoo.org \
--to=kumba@gentoo.org \
--cc=giuseppe@eppesuigoccas.homedns.org \
--cc=linux-mips@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.