From: Ralf Baechle <ralf@linux-mips.org>
To: Pete Popov <ppopov@mvista.com>
Cc: Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: R4600 V1.7 errata
Date: Wed, 4 Feb 2004 21:04:23 +0100 [thread overview]
Message-ID: <20040204200423.GA20197@linux-mips.org> (raw)
In-Reply-To: <1075910389.1170.42.camel@localhost.localdomain>
On Wed, Feb 04, 2004 at 07:59:49AM -0800, Pete Popov wrote:
> > [...]
> > > 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.
> >
> > Works now. Thanks, guys.
>
> The latest cache updates break the Au1x kernel. I don't know yet exactly
> what the problem is, but I tested with a snapshot before and after the
> updates.
The cache updates should specifically only affects systems that explicitly
enable the cache workaround in <asm/war.h>; for any other the compiler
should totally eleminate the workaround from the binary.
Therefore my first guess would be pg-r4k.c.
Ralf
prev parent reply other threads:[~2004-02-04 20:04 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
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 [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=20040204200423.GA20197@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@mvista.com \
/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.