From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: Re: R4600 V1.7 errata
Date: Tue, 3 Feb 2004 12:52:36 +0100 [thread overview]
Message-ID: <20040203115236.GB28340@linux-mips.org> (raw)
In-Reply-To: <20040203114252.GA27810@icm.edu.pl>
On Tue, Feb 03, 2004 at 12:42:53PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> On Tue, Feb 03, 2004 at 12:39:28PM +0100, Ralf Baechle wrote:
> [...]
> > Jorik was so friendly to track down the patch in CVS that broke the R4600
> > V1.7 back in time. With that as a start it was fairly easy to isolate the
> > problem further. Seems we became victim of some erratum that affects the
> > operation of indexed I-cache flushes only. Last night I commited a patch
> > that provides an optimized solution for the problem.
>
> I assume it's safe to test it now? I'll build it for my R4600 V2.0 and
> report in a while. Stay tuned.
2.0 requires different workarounds which are already in place and functional
since quite some time. We still lacking a fix for one important erratum of
the 2.0 but it seems pretty stable without.
Chip revs later than 2.0 do identify as 2.0 so if you're lucky your processor
is actually a post-2.0 and working just fine ...
Ralf
next prev parent reply other threads:[~2004-02-03 11:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 10:22 linux 2.4 and Indy Jorik Jonker
2004-01-29 10:40 ` Kumba
2004-01-30 10:59 ` Jorik Jonker
2004-01-30 11:12 ` Dominik 'Rathann' Mierzejewski
2004-01-30 20:49 ` Jorik Jonker
2004-01-30 21:01 ` Jorik Jonker
2004-01-31 3:04 ` Ralf Baechle
2004-01-31 14:10 ` Jorik Jonker
2004-02-01 4:52 ` R4600 V1.7 errata Ralf Baechle
2004-02-03 11:39 ` Ralf Baechle
2004-02-03 11:42 ` Dominik 'Rathann' Mierzejewski
2004-02-03 11:52 ` Ralf Baechle [this message]
2004-02-03 15:43 ` Maciej W. Rozycki
2004-02-03 16:12 ` Ralf Baechle
2004-02-03 16:20 ` Maciej W. Rozycki
2004-02-04 15:48 ` Dominik 'Rathann' Mierzejewski
2004-02-04 15:59 ` Pete Popov
2004-02-04 20:04 ` Ralf Baechle
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=20040203115236.GB28340@linux-mips.org \
--to=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox