From: Markus Dahms <mad@automagically.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: 2.6 on IP22 (Indy)
Date: Tue, 19 Jul 2005 20:21:02 +0200 [thread overview]
Message-ID: <20050719182102.GA3727@gaspode.automagically.de> (raw)
In-Reply-To: <Pine.LNX.4.61L.0506291747550.31188@blysk.ds.pg.gda.pl>
Hello Maciej,
[R4600PC problems]
> Well, they are not meant to be errata-compatible. ;-) I haven't been
> able to locate any reference for tlbp being problematic on the R4600, in
> particular not in the chip errata document, and the old handlers used to
> have a nop before that instruction unconditionally (perhaps just in case
> ;-) ), so the problem was covered. If it fixes the problem for you, then
> it should probably be applied, too.
I just built a 64-bit kernel from clean CVS and had to apply the patch
below again to get it to userspace. Maybe it just hides the real error
but at least "it works for me" [tm].
Please apply to CVS if there are no objections.
Markus
--- a/arch/mips/mm/tlbex.c 2005-07-19 20:12:32.000000000 +0200
+++ b/arch/mips/mm/tlbex.c 2005-07-19 20:10:29.000000000 +0200
@@ -779,6 +779,7 @@
static __init void __attribute__((unused)) build_tlb_probe_entry(u32 **p)
{
switch (current_cpu_data.cputype) {
+ case CPU_R4600:
case CPU_R5000:
case CPU_R5000A:
case CPU_NEVADA:
next prev parent reply other threads:[~2005-07-19 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 10:07 2.6 on IP22 (Indy) Markus Dahms
2005-06-27 13:17 ` Maciej W. Rozycki
2005-06-27 14:18 ` Markus Dahms
2005-06-27 20:54 ` Maciej W. Rozycki
2005-06-28 6:21 ` Markus Dahms
2005-06-28 9:05 ` Maciej W. Rozycki
2005-06-28 10:20 ` Markus Dahms
2005-06-28 11:25 ` Maciej W. Rozycki
2005-06-28 17:04 ` Markus Dahms
2005-06-29 16:54 ` Maciej W. Rozycki
2005-07-19 18:21 ` Markus Dahms [this message]
2005-07-20 1:45 ` Thiemo Seufer
2005-06-28 12:23 ` Stephen P. Becker
2005-06-28 12:44 ` Maciej W. Rozycki
2005-06-28 13:03 ` Stephen P. Becker
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=20050719182102.GA3727@gaspode.automagically.de \
--to=mad@automagically.de \
--cc=linux-mips@linux-mips.org \
--cc=macro@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