From: "M. Warner Losh" <imp@bsdimp.com>
To: paul@codesourcery.com
Cc: qemu-devel@nongnu.org, octane@alinto.com
Subject: Re: [Qemu-devel] Support For Octeon/Cavium CPU (MIPS system)
Date: Thu, 22 May 2008 10:17:15 -0600 (MDT) [thread overview]
Message-ID: <20080522.101715.-233685094.imp@bsdimp.com> (raw)
In-Reply-To: <200805221704.00480.paul@codesourcery.com>
In message: <200805221704.00480.paul@codesourcery.com>
Paul Brook <paul@codesourcery.com> writes:
: > : > I know that Cavium/octeon board are MIPS CPU.
: > :
: > : Not really. They're MIPS with extra weirdness.
: >
: > All SoCs are MIPS with extra documented weirdness. The OCTEON CPUs
: > aren't documented in a public...
:
: The Cavium cores are weirder than most. It doesn't use the normal MIPS ISA.
: Most SoC are a standard mips core (r4k, etc.) with a bunch of peripherals.
Yes, they do use the noraml MIPS ISA. It is a MIPS64r2 part. It does
have a bunch of additional instructions that are leveraged off the CP2
coprocessor for crypto and related things. Its cache is different
too, but every platform's cache is different. There's a number of
hacks present to allow different images to run on different core.
Or maybe this is what you are saying :-
Warner
next prev parent reply other threads:[~2008-05-22 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 10:48 [Qemu-devel] Support For Octeon/Cavium CPU (MIPS system) octane indice
2008-05-22 13:27 ` Paul Brook
2008-05-22 15:55 ` M. Warner Losh
2008-05-22 16:03 ` Paul Brook
2008-05-22 16:17 ` M. Warner Losh [this message]
2008-05-22 16:52 ` Thiemo Seufer
2008-05-22 22:04 ` Jamie Lokier
2008-05-22 15:47 ` M. Warner Losh
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=20080522.101715.-233685094.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=octane@alinto.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).