From: Ryan Martindale <ryan@qsicorp.com>
To: linux-mips@oss.sgi.com
Subject: fpu woes (TX3912)
Date: Mon, 15 Jul 2002 10:04:35 -0700 [thread overview]
Message-ID: <3D3300A3.FD50EDEA@qsicorp.com> (raw)
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.
Ryan Martindale
QSI Corporation
next reply other threads:[~2002-07-15 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 17:04 Ryan Martindale [this message]
2002-07-15 16:24 ` fpu woes (TX3912) Kevin D. Kissell
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=3D3300A3.FD50EDEA@qsicorp.com \
--to=ryan@qsicorp.com \
--cc=linux-mips@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 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.