From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@linux-mips.org
Subject: Re: R4600 V1.7 errata
Date: Tue, 3 Feb 2004 17:12:02 +0100 [thread overview]
Message-ID: <20040203161202.GC1018@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0402031636210.16076@jurand.ds.pg.gda.pl>
On Tue, Feb 03, 2004 at 04:43:19PM +0100, Maciej W. Rozycki wrote:
> > 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.
>
> Well, I can actually see two problems: #4 that is fairly easy to handle
> and #7 which is painful and which is unfortunately present with the R4700
> as well.
If #7 would only affect the R4700 the world would peachy ... To my
knowledge the dusty box here in a corner is the only R4700 that ever ran
Linux ...
Under a different bug number this bug also affects the R4600 V1.x; it's
fixed in post-2.0 R4600 (which all identify as 2.0) and post-1.1 R4700.
Since a workaround may be a bit performance sensitive I think I'll try if
it can be probed for reliably.
Ralf
next prev parent reply other threads:[~2004-02-03 16:12 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
2004-02-03 15:43 ` Maciej W. Rozycki
2004-02-03 16:12 ` Ralf Baechle [this message]
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=20040203161202.GC1018@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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.