From: "Keryell, Ronan (XILINX LABS)" <ronan.keryell@amd.com>
To: Rob Herring <robh@kernel.org>, "Simek, Michal" <michal.simek@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"monstr@monstr.eu" <monstr@monstr.eu>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"git@xilinx.com" <git@xilinx.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Conor Dooley <conor@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH] dt-bindings: riscv: cpus: Add AMD MicroBlaze V compatible
Date: Wed, 8 Nov 2023 18:35:25 +0000 [thread overview]
Message-ID: <5d2563a8-dd26-417b-a3ba-1b12b6c37bae@amd.com> (raw)
In-Reply-To: <20231108171203.GA2434548-robh@kernel.org>
On 11/8/23 09:12, Rob Herring wrote:
> On Mon, Nov 06, 2023 at 12:37:47PM +0100, Michal Simek wrote:
>> MicroBlaze V is new AMD/Xilinx soft-core 32bit RISC-V processor IP.
>> It is hardware compatible with classic MicroBlaze processor.
>
> How is that possible? It's a different instruction set, right? I suppose
> the IP interfaces (signals) are the same/compatible.
Coincidentally, I asked myself the same question, so I asked my former
manager who designed the ancestor of this processor. The answer is
| It is still the same MicroBlaze pipeline just with a different
| instruction decoder up front. The “macro ops” are now RISC V
| instructions, the “micro-ops” are still the same operations in the
| various MicroBlaze pipeline stages.
So, yes, all the hardware interface is the same.
--
Ronan KERYELL, Research Labs / San José, California.
AMD Research and Advanced Development.
next prev parent reply other threads:[~2023-11-08 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 11:37 [PATCH] dt-bindings: riscv: cpus: Add AMD MicroBlaze V compatible Michal Simek
2023-11-08 17:12 ` Rob Herring
2023-11-08 18:35 ` Keryell, Ronan (XILINX LABS) [this message]
2023-11-09 17:15 ` Conor Dooley
2023-12-20 15:15 ` Palmer Dabbelt
2024-01-05 14:44 ` Michal Simek
2023-12-20 13:50 ` Michal Simek
2024-01-05 21:50 ` patchwork-bot+linux-riscv
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=5d2563a8-dd26-417b-a3ba-1b12b6c37bae@amd.com \
--to=ronan.keryell@amd.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michal.simek@amd.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.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).