From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: "Pete Popov" <ppopov@mvista.com>,
"Steve Johnson" <stevej@ridgerun.com>, <linux-mips@oss.sgi.com>
Subject: Re: floating point on Nevada cpu
Date: Sat, 27 Jan 2001 11:16:38 -0800 [thread overview]
Message-ID: <20010127111638.H867@bacchus.dhis.org> (raw)
In-Reply-To: <010601c08780$d0b8a7a0$0deca8c0@Ulysses>; from kevink@mips.com on Fri, Jan 26, 2001 at 11:14:38AM +0100
On Fri, Jan 26, 2001 at 11:14:38AM +0100, 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)
It's not in the CVS 2.2 kernel. I've added this patch to my kernel and
will commit it when I'm online again.
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Pete Popov <ppopov@mvista.com>,
Steve Johnson <stevej@ridgerun.com>,
linux-mips@oss.sgi.com
Subject: Re: floating point on Nevada cpu
Date: Sat, 27 Jan 2001 11:16:38 -0800 [thread overview]
Message-ID: <20010127111638.H867@bacchus.dhis.org> (raw)
Message-ID: <20010127191638.RJJrrNXVeZQ3SiwyE8Cu6VsrLC9nZR0EIT8Haftbe2M@z> (raw)
In-Reply-To: <010601c08780$d0b8a7a0$0deca8c0@Ulysses>; from kevink@mips.com on Fri, Jan 26, 2001 at 11:14:38AM +0100
On Fri, Jan 26, 2001 at 11:14:38AM +0100, 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)
It's not in the CVS 2.2 kernel. I've added this patch to my kernel and
will commit it when I'm online again.
Ralf
next prev parent reply other threads:[~2001-01-28 2:55 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
2001-01-26 13:57 ` Kevin D. Kissell
2001-01-26 13:57 ` Kevin D. Kissell
2001-01-27 19:16 ` Ralf Baechle [this message]
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=20010127111638.H867@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=ppopov@mvista.com \
--cc=stevej@ridgerun.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