From: "Kevin D. Kissell" <kevink@mips.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Franck <vagabon.xyz@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] Add support for 4KS cpu.
Date: Tue, 04 Oct 2005 15:54:47 +0200 [thread overview]
Message-ID: <434289A7.50007@mips.com> (raw)
In-Reply-To: <Pine.LNX.4.61L.0510041358300.10696@blysk.ds.pg.gda.pl>
Maciej W. Rozycki wrote:
> On Tue, 4 Oct 2005, Kevin D. Kissell wrote:
>
>
>>FWIW, the 4KSc is a strict superset of the 4Kc (anticipating
>>*some* of the Release 2 features, but not requiring them to be
>>used) and the 4KSd is a strict superset of the 4KE. I would
>>not recommend configuring CPU_MIPS32_R2 for the 4KSc.
>
>
> Well, the patch asked GCC to use the instruction set of the "4kec" CPU
> for both (and also the "mips32r2" ISA, but that's overridden by the
> former), so it must have been incorrect in the first place
Which was sort-of why I replied. In particular, the MIPS32R2 bitfield
instructions will probably cause a reserved instruction fault on a 4KSc.
Regards,
Kevin K.
next prev parent reply other threads:[~2005-10-04 13:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 8:49 [PATCH] Add support for 4KS cpu Franck
2005-10-04 11:34 ` Maciej W. Rozycki
2005-10-04 12:38 ` Kevin D. Kissell
2005-10-04 13:29 ` Maciej W. Rozycki
2005-10-04 13:54 ` Kevin D. Kissell [this message]
2005-10-04 15:18 ` Franck
2005-10-04 16:01 ` Maciej W. Rozycki
2005-10-04 17:33 ` Franck
2005-10-05 6:55 ` Franck
2005-10-05 13:22 ` Maciej W. Rozycki
2005-10-05 18:04 ` Franck
2005-10-05 7:00 ` Franck
2005-10-05 9:46 ` Kevin D. Kissell
2005-10-05 13:20 ` Franck
2005-10-04 13:10 ` Franck
2005-10-04 13:54 ` Maciej W. Rozycki
2005-10-04 15:10 ` Franck
2005-10-04 17:11 ` Maciej W. Rozycki
2005-10-04 14:17 ` Ralf Baechle
2005-10-04 14:06 ` 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=434289A7.50007@mips.com \
--to=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=vagabon.xyz@gmail.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