Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <nemoto@toshiba-tops.co.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: CVS Update@ftp.linux-mips.org: linux
Date: Mon, 30 Sep 2002 08:24:43 +0200	[thread overview]
Message-ID: <20020930082443.A2046@linux-mips.org> (raw)
In-Reply-To: <20020930.135717.39150888.nemoto@toshiba-tops.co.jp>; from nemoto@toshiba-tops.co.jp on Mon, Sep 30, 2002 at 01:57:17PM +0900

On Mon, Sep 30, 2002 at 01:57:17PM +0900, Atsushi Nemoto wrote:

> It seems some necessary codes for non-r4k CPUs were lost by this change.

Mercyfully sent to /dev/null you wanted to say.

> +	case CPU_SB1:
> +		/*
> +		 * XXX - This should be folded in to the "cleaner" handling,
> +		 * above
> +		 */
> +		memcpy((void *)(KSEG0 + 0x180), &except_vec3_r4000, 0x80);
> +		break;

This was a bug. Except_vec3_r4000 is only intended for the R4000/R4400, the
only MIPS CPUs which support the virtual coherency exception.  SB1 should
use except_vec4_generic instead.

> +	case CPU_TX39XX:
> +		memcpy((void *)(KSEG0 + 0x80), &except_vec3_generic, 0x80);

Eeek, will fix.  Consider the switch gone however.

  Ralf

  reply	other threads:[~2002-09-30  6:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020929014920Z1121744-9213+239@linux-mips.org>
2002-09-30  4:57 ` CVS Update@ftp.linux-mips.org: linux Atsushi Nemoto
2002-09-30  6:24   ` Ralf Baechle [this message]
2002-10-01  1:46   ` Mike Nugent
2002-10-01 12:01     ` Ralf Baechle
     [not found] <20020930165347Z1122169-9213+249@linux-mips.org>
2002-10-03  3:17 ` Atsushi Nemoto
2002-10-03  9:41   ` Ralf Baechle
     [not found] <20021026014147Z1124126-9213+559@linux-mips.org>
2002-10-26  1:52 ` Maciej W. Rozycki

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=20020930082443.A2046@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=nemoto@toshiba-tops.co.jp \
    /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