Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Eric Christopher <echristo@redhat.com>,
	Mark and Janice Juszczec <juszczec@hotmail.com>,
	linux-mips@linux-mips.org
Subject: Re: r3000 instruction set
Date: Sun, 22 Feb 2004 22:03:17 -0500	[thread overview]
Message-ID: <40396D75.7090405@realitydiluted.com> (raw)
In-Reply-To: <001001c3f98e$2270dcc0$10eca8c0@grendel>

Kevin D. Kissell wrote:
> 
> The 3900 family should run MIPS I code compiled for the R3000.
>
Yep.

> The 3912 has no FPU, but if you're running on any contemporary
> MIPS/Linux kernel and library system, you neither need nor want
> soft-float.  The kernel does FP instruction emulation.  Running soft-float
> would make for faster, if larger, code, but requires that the whole
> system, particularly glibc, be built for soft-float, which is rarely done
> (and the last time I tried it, didin't quite work with the standard
> glibc sources out-of-the-box). 
> 
Correct. I use the FP emulator in Linux for my TX3917/PR31700 stuff. I
have had no problems. Current glibc has assembly code that assumes hardware
floating point which is why building for soft-float does not work out of
the box. There are probably some patches out there to rectify that. My
personal choice, use uClibc (http://uclibc.org/) for your C runtime. I wrote
the dynamic linker loader for MIPS and would highly recommend you try it out.
I would really like to see more testing of it.

Also, I have some documents for the 3912 on my FTP site:

    ftp://ftp.realitydiluted.com/docs/Toshiba
    ftp://ftp.realitydiluted.com/docs/Philips

It should be noted that the Toshiba TX3912 and the Philips PR31700 are
identical cores. There was definitely some cross-licensing going on there.
Perhaps Kevin or Dominic would know this in more detail, but it is not
really that important.

-Steve

  parent reply	other threads:[~2004-02-23  3:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-22  3:02 r3000 instruction set Mark and Janice Juszczec
2004-02-22  3:15 ` Michael Uhler
2004-02-22  9:32 ` Kevin D. Kissell
2004-02-22  9:32   ` Kevin D. Kissell
2004-02-22 12:31 ` Dominic Sweetman
2004-02-22 19:13 ` Eric Christopher
2004-02-22 21:52   ` Kevin D. Kissell
2004-02-22 21:52     ` Kevin D. Kissell
2004-02-23  3:03     ` Steven J. Hill [this message]
2004-02-23  7:03       ` Kevin D. Kissell
2004-02-23  7:03         ` Kevin D. Kissell
2004-02-23  3:37     ` Eric Christopher
2004-02-23  7:11       ` Kevin D. Kissell
2004-02-23  7:11         ` Kevin D. Kissell
2004-02-23  7:29         ` Eric Christopher
  -- strict thread matches above, loose matches on Subject: below --
2004-02-23 16:56 Mark and Janice Juszczec
2004-02-23 17:07 ` Michael Uhler
2004-02-23 17:13 ` Maciej W. Rozycki
2004-02-23 17:21 ` Kevin D. Kissell
2004-02-23 17:21   ` Kevin D. Kissell
2004-02-23 17:59 ` Dominic Sweetman
2004-02-23 20:48 Mark and Janice Juszczec
2004-02-23 22:46 ` Kevin D. Kissell
2004-02-23 22:46   ` Kevin D. Kissell
2004-03-01 15:38 Mark and Janice Juszczec

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=40396D75.7090405@realitydiluted.com \
    --to=sjhill@realitydiluted.com \
    --cc=echristo@redhat.com \
    --cc=juszczec@hotmail.com \
    --cc=kevink@mips.com \
    --cc=linux-mips@linux-mips.org \
    /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