From: Kumba <kumba@gentoo.org>
To: post@pfrst.de
Cc: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>,
linux-mips@linux-mips.org
Subject: Re: R1000 status
Date: Sat, 19 May 2007 15:01:33 -0400 [thread overview]
Message-ID: <464F498D.4070205@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0705190928580.182@Indigo2.Peter>
peter fuerst wrote:
>
> Hello,
>
> yes, the GCC-patches should do the trick. And without a significant
> performance decrease, as i was told in the latest success-report (see
> http://sgi.sedlacek.biz/).
>
> kind regards
Interesting, I'm curious to see this guy's patches to see what he does different
for the IP32 R10K stuff. Whether it's the same thing I did (mod IP28 patches
and build w/ gcc cache barriers on load and store ops), or if he went an extra
step and added code to protect the scsi and networking drivers.
--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
next 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 [this message]
2007-05-19 19:00 ` Kumba
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=464F498D.4070205@gentoo.org \
--to=kumba@gentoo.org \
--cc=giuseppe@eppesuigoccas.homedns.org \
--cc=linux-mips@linux-mips.org \
--cc=post@pfrst.de \
/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