From: Eric Christopher <echristo@redhat.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Mark and Janice Juszczec <juszczec@hotmail.com>,
linux-mips@linux-mips.org
Subject: Re: r3000 instruction set
Date: Sun, 22 Feb 2004 23:29:23 -0800 [thread overview]
Message-ID: <1077521360.4719.0.camel@dzur.sfbay.redhat.com> (raw)
In-Reply-To: <001901c3f9dc$3a46b6a0$10eca8c0@grendel>
> I think you may be confusing MIPS I and MIPS II. I'm pretty darn certain
> that the TX39 inplemented all of MIPS I, most of MIPS II, plus a MADD
> extension. I'm not going to go instruction counting this morning, but the
> TX39 spec declares up-front that it's a superset of the R3000A.
Me either so until I guess the guy says which instruction is at fault
we'll leave it be. :)
-eric
--
Eric Christopher <echristo@redhat.com>
next prev parent reply other threads:[~2004-02-23 7:29 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
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 [this message]
-- 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=1077521360.4719.0.camel@dzur.sfbay.redhat.com \
--to=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