Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Alice Hennessy <ahennessy@mvista.com>
Cc: Carsten Langgaard <carstenl@mips.com>,
	Atsushi Nemoto <nemoto@toshiba-tops.co.jp>,
	ajob4me@21cn.com, linux-mips@oss.sgi.com
Subject: Re: Toshiba TX3927 board boot problem.
Date: Tue, 30 Oct 2001 01:32:23 +0100	[thread overview]
Message-ID: <20011030013223.B6614@dea.linux-mips.net> (raw)
In-Reply-To: <3BDDF193.B6405A7F@mvista.com>; from ahennessy@mvista.com on Mon, Oct 29, 2001 at 04:17:23PM -0800

On Mon, Oct 29, 2001 at 04:17:23PM -0800, Alice Hennessy wrote:

> > This doesn't look right, you still need to enable the CU1 bit in the
> > status register to let the FP emulator kick-in.  FPU-less CPUs should
> > take a coprocessor unusable exception on any floating-point instructions.
> > I have been running this on several FPU-less CPUs, and it works fine for
> me.
> 
> Maybe the FPU-less CPUs you have been using define the CU1 bit as reserved
> or is unused (ignore on write, zero on read)? The TX3927 actually allows
> the setting of the CU1 bit.  Have you seen a case where you need to set
> the CU1 bit for the emulation to kick-in?   I would think that the CU1
> bit should never be set to one for FPU-less CPUs.

There are subtle differences in how CUx bits for unimplemented coprocessors
are handled in the various processors.  MIPS32 and MIPS64 specifies the
behaviour as 0 on read, writes ignored; previous processors such as the
R4000 handled this differently and as a consequence a fp instruction on
a fpu-less r4000 class cpu may either throw a CU or a reserved instruction
exception.  To make things easier for everybody this is documented in the
R10000 user's manual ...

  Ralf

  reply	other threads:[~2001-10-30  0:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20011026095319.1C4BBB474@topsms.toshiba-tops.co.jp>
2001-10-26 13:58 ` Toshiba TX3927 board boot problem Atsushi Nemoto
2001-10-29  7:02   ` Atsushi Nemoto
2001-10-29  8:32     ` Carsten Langgaard
2001-10-30  0:17       ` Alice Hennessy
2001-10-30  0:32         ` Ralf Baechle [this message]
2001-10-30  2:25           ` Alice Hennessy
2001-10-30  8:36             ` Carsten Langgaard
2001-10-30 14:13               ` Ralf Baechle
2001-10-30 14:17                 ` Carsten Langgaard
2001-10-30  3:14         ` Atsushi Nemoto
2001-10-30  8:20         ` Carsten Langgaard
2001-10-30 14:55           ` Ralf Baechle
2001-10-31  2:58             ` Atsushi Nemoto
2001-10-31  4:06               ` Ralf Baechle
2001-10-31  4:30                 ` Atsushi Nemoto
2001-10-31  4:31                   ` Ralf Baechle
2001-10-31  5:07                     ` Daniel Jacobowitz
2001-10-26  9:49 8route

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=20011030013223.B6614@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=ahennessy@mvista.com \
    --cc=ajob4me@21cn.com \
    --cc=carstenl@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --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