Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Greg Weeks <greg.weeks@timesys.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: another 4kc machine check.
Date: Mon, 11 Apr 2005 15:47:12 -0400	[thread overview]
Message-ID: <425AD440.5050600@timesys.com> (raw)
In-Reply-To: <4256B524.2080509@timesys.com>

[-- Attachment #1: Type: text/plain, Size: 142 bytes --]

This patch appears to fix my machine check problem on the 4kc. The 4kc 
shouldn't need an ssnop here, but this appears to fix it.

Greg Weeks

[-- Attachment #2: mips.4kc.tlb.patch --]
[-- Type: text/x-patch, Size: 331 bytes --]

--- mips-malta4kcle-basic/arch/mips/mm/tlbex.c-orig
+++ mips-malta4kcle-basic/arch/mips/mm/tlbex.c
@@ -847,7 +847,6 @@
 
 	case CPU_R10000:
 	case CPU_R12000:
-	case CPU_4KC:
 	case CPU_SB1:
 	case CPU_4KSC:
 	case CPU_20KC:
@@ -874,6 +873,7 @@
 		tlbw(p);
 		break;
 
+	case CPU_4KC:
 	case CPU_4KEC:
 	case CPU_24K:
 		i_ehb(p);

  reply	other threads:[~2005-04-11 19:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-07 14:06 another 4kc machine check Greg Weeks
2005-04-08 14:45 ` Greg Weeks
2005-04-08 16:13   ` Ralf Baechle
2005-04-08 16:45     ` Greg Weeks
2005-04-11 19:47       ` Greg Weeks [this message]
2005-04-11 20:27         ` Kevin D. Kissell
2005-04-11 20:27           ` Kevin D. Kissell
2005-04-12 14:52           ` Greg Weeks
2005-04-12 15:22           ` Maciej W. Rozycki
2005-04-12 16:38             ` Kevin D. Kissell
2005-04-12 16:38               ` Kevin D. Kissell
2005-04-12 16:52               ` Greg Weeks
2005-04-12 19:12                 ` Greg Weeks
2005-04-11 20:42         ` Kevin D. Kissell
2005-04-11 20:42           ` Kevin D. Kissell
2005-06-10 16:39         ` Chris Wedgwood

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=425AD440.5050600@timesys.com \
    --to=greg.weeks@timesys.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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