Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Steve Johnson <stevej@ridgerun.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Pete Popov <ppopov@mvista.com>, linux-mips@oss.sgi.com
Subject: Re: floating point on Nevada cpu
Date: Fri, 26 Jan 2001 06:01:12 -0700	[thread overview]
Message-ID: <3A717518.B1CAFEDC@ridgerun.com> (raw)
In-Reply-To: 010601c08780$d0b8a7a0$0deca8c0@Ulysses

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

"Kevin D. Kissell" wrote:

> I had essentially the same problem at MIPS a year or two ago,
> and I could have *sworn* that my fix, which ORed ST0_FR into
> the initial Status register value set in the startup assembly code,
> had made it into the standard distributions.  It's at about line 530
> of head.S, where a term is added to make the instruction
>
> li t1,~(ST0_CU1|ST0_CU2|ST0_CU3|ST0_KX|ST0_SX|ST0_FR)
>
> I spent days thinking it was a mipsel library problem,
> because it only turned up when I tried exercising a
> little-endian version of the same kernel that worked
> sell big-endian on the Indy.  But of course it was all
> due to the mipsel system having a boot-prom that
> cleverly enabled all the FP registers for me...
>
>             Kevin K.

Kevin,

    Your/Flo's/Ralf's thread in the MIPS Linux archives from last January was
what clued me into the ST0_FR setting in the first place.  Ralf gave arguments
why he wouldn't take your change at that time, which is why that line isn't in
the 2.4.x kernel.

    Steve


[-- Attachment #2: Card for Steve Johnson --]
[-- Type: text/x-vcard, Size: 355 bytes --]

begin:vcard 
n:Johnson;Steve
tel;fax:208-331-2227
tel;work:208-331-2226x11
x-mozilla-html:TRUE
url:http://www.ridgerun.com
org:RidgeRun, Inc.
version:2.1
email;internet:stevej@ridgerun.com
title:Senior Kernel Developer
adr;quoted-printable:;;RidgeRun, Inc.=0D=0A200 N 4th St, Suite 101		;Boise;ID;83702;USA
x-mozilla-cpt:;27936
fn:Steve Johnson
end:vcard

  parent reply	other threads:[~2001-01-26 13:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25  2:28 floating point on Nevada cpu Pete Popov
2001-01-25  2:33 ` Justin Carlson
2001-01-25  2:52   ` Pete Popov
2001-01-25  2:57     ` Justin Carlson
2001-01-25  2:57       ` Justin Carlson
2001-01-25  3:05   ` Pete Popov
2001-01-25  3:16     ` Justin Carlson
2001-01-25 14:54       ` Steve Johnson
2001-01-25 18:02         ` Pete Popov
2001-01-26 10:14           ` Kevin D. Kissell
2001-01-26 10:14             ` Kevin D. Kissell
2001-01-26 13:01             ` Steve Johnson [this message]
2001-01-26 13:57               ` Kevin D. Kissell
2001-01-26 13:57                 ` Kevin D. Kissell
2001-01-27 19:16             ` Ralf Baechle
2001-01-27 19:16               ` Ralf Baechle
2001-01-25 17:26       ` Ralf Baechle
2001-01-25 20:01         ` Justin Carlson
2001-01-25 22:12 ` Ralf Baechle
2001-01-26  7:53   ` Carsten Langgaard
  -- strict thread matches above, loose matches on Subject: below --
2001-01-25 17:37 Ralf Baechle

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=3A717518.B1CAFEDC@ridgerun.com \
    --to=stevej@ridgerun.com \
    --cc=kevink@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ppopov@mvista.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