Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Carsten Langgaard <carstenl@mips.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Alice Hennessy <ahennessy@mvista.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 15:17:18 +0100	[thread overview]
Message-ID: <3BDEB66E.AFD71BBA@mips.com> (raw)
In-Reply-To: 20011030151308.B10165@dea.linux-mips.net

Ralf Baechle wrote:

> On Tue, Oct 30, 2001 at 09:36:01AM +0100, Carsten Langgaard wrote:
>
> > > So,  we should not set CU1 generically for FPU-less CPUs especially since a
> > > known problem exists
> > > for the tx3927?  Ie, qualify all setting of CU1 as follows:
> > >
> > > if (mips_cpu.options & MIPS_CPU_FPU)
> > >                    set_cp0_status(ST0_CU1);
> >
> > And while we are at it, could we handle the CP0 hazard of 4 nops, between
> > setting the CU1 bit in the status register and executing
> > the first floating point instruction, on CPU which got a FPU.
>
> Which CPUs actually need four nops?
>
> Just working on a patch; I found a bunch more place where we were playing
> with the CU1 bit.

The MIPS32 spec specify 4 nops.

>
>   Ralf

--
_    _ ____  ___   Carsten Langgaard   Mailto:carstenl@mips.com
|\  /|||___)(___   MIPS Denmark        Direct: +45 4486 5527
| \/ |||    ____)  Lautrupvang 4B      Switch: +45 4486 5555
  TECHNOLOGIES     2750 Ballerup       Fax...: +45 4486 5556
                   Denmark             http://www.mips.com

  reply	other threads:[~2001-10-30 14:17 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
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 [this message]
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=3BDEB66E.AFD71BBA@mips.com \
    --to=carstenl@mips.com \
    --cc=ahennessy@mvista.com \
    --cc=ajob4me@21cn.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=nemoto@toshiba-tops.co.jp \
    --cc=ralf@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox