All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: "Ryan Martindale" <ryan@qsicorp.com>, <linux-mips@oss.sgi.com>
Subject: Re: fpu woes (TX3912)
Date: Mon, 15 Jul 2002 18:24:16 +0200	[thread overview]
Message-ID: <01c401c22c1c$1973a170$10eca8c0@grendel> (raw)
In-Reply-To: 3D3300A3.FD50EDEA@qsicorp.com

> I'm using the tx3912 processor for an embedded device and since it
> doesn't have an fpu, I don't have coprocessor #1.  Recently, I remember
> seeing a fix in process.c for exit_thread and flush_thread, and did
> apply it - but there still is a problem (at least for me). In traps.c,
> the save_fp_context and restore_fp_context are set to _save_fp_context
> (in r2300_fpu.S) which don't check to see if I have a coprocessor
> available. As I am rather new to the linux/linux-mips development world,
> I thought I'd give a heads up (it is causing my embedded system to
> crash). Any direction on fixing it would be welcome, but I'm not sure
> I'll get to the point where I will submit any patches any time soon.

People break things from time to time, but at least at one point
in history, R3xxx platforms were correctly supported by the
FPU emulator code.  Looking at the source code on my 
system, it looks like traps.c has been "cleaned up" in a
somewhat wierd manner, such that the test for whether
there is an FPU happens redundantly, once in the specific
case of a 4K family CPU (which you would not hit on your
TX39), and again just after the switch on the CPU type.
Did someone screw up the setting of mips_cpu.options
for a TX39xx or something?  Is that code missing from
the sources that you're using?  Are you sure that it isn't
something else blowing up on you?  There have been
mods made locally here and there that might have
broken the FPU emulator for R3xxx platforms, but
I didn't think that any of them were up on OSS.sgi.com
or kernel.org.

            Regards,

            Kevin K.

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Ryan Martindale <ryan@qsicorp.com>, linux-mips@oss.sgi.com
Subject: Re: fpu woes (TX3912)
Date: Mon, 15 Jul 2002 18:24:16 +0200	[thread overview]
Message-ID: <01c401c22c1c$1973a170$10eca8c0@grendel> (raw)
Message-ID: <20020715162416.fCXmIspI6v8k9W3uKeR7ixlkByUjN6nkJ3ojEolxUHw@z> (raw)
In-Reply-To: 3D3300A3.FD50EDEA@qsicorp.com

> I'm using the tx3912 processor for an embedded device and since it
> doesn't have an fpu, I don't have coprocessor #1.  Recently, I remember
> seeing a fix in process.c for exit_thread and flush_thread, and did
> apply it - but there still is a problem (at least for me). In traps.c,
> the save_fp_context and restore_fp_context are set to _save_fp_context
> (in r2300_fpu.S) which don't check to see if I have a coprocessor
> available. As I am rather new to the linux/linux-mips development world,
> I thought I'd give a heads up (it is causing my embedded system to
> crash). Any direction on fixing it would be welcome, but I'm not sure
> I'll get to the point where I will submit any patches any time soon.

People break things from time to time, but at least at one point
in history, R3xxx platforms were correctly supported by the
FPU emulator code.  Looking at the source code on my 
system, it looks like traps.c has been "cleaned up" in a
somewhat wierd manner, such that the test for whether
there is an FPU happens redundantly, once in the specific
case of a 4K family CPU (which you would not hit on your
TX39), and again just after the switch on the CPU type.
Did someone screw up the setting of mips_cpu.options
for a TX39xx or something?  Is that code missing from
the sources that you're using?  Are you sure that it isn't
something else blowing up on you?  There have been
mods made locally here and there that might have
broken the FPU emulator for R3xxx platforms, but
I didn't think that any of them were up on OSS.sgi.com
or kernel.org.

            Regards,

            Kevin K.

  reply	other threads:[~2002-07-15 16:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15 17:04 fpu woes (TX3912) Ryan Martindale
2002-07-15 16:24 ` Kevin D. Kissell [this message]
2002-07-15 16:24   ` Kevin D. Kissell
2002-07-15 17:48   ` Ryan Martindale
2002-07-15 18:04     ` Kevin D. Kissell
2002-07-15 18:04       ` Kevin D. Kissell
2002-07-16 14:03       ` 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='01c401c22c1c$1973a170$10eca8c0@grendel' \
    --to=kevink@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ryan@qsicorp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.