linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pintu.ping@gmail.com (Pintu Agarwal)
To: linux-riscv@lists.infradead.org
Subject: RISCV64 SoC Architecture diagram
Date: Thu, 22 Nov 2018 13:04:03 +0530	[thread overview]
Message-ID: <CAOuPNLiQWiqwkhKXyKV08mWz-Zfis8O3dHB0W5UVfroLU=W4Rw@mail.gmail.com> (raw)

Hi All,

For the education purpose, we need RISCV SoC internal architecture
diagram which can give a pictorial overview of RISCV internals.
As part of study, we want to compare this with ARMv8 architecture.

If anybody have it please share.

Also, if anybody have risv64 benchmarking data with arm64, please
share this as well.


Thanks,
Pintu

WARNING: multiple messages have this Message-ID (diff)
From: Pintu Agarwal <pintu.ping@gmail.com>
To: isa-dev@groups.riscv.org, linux-riscv@lists.infradead.org,
	 sw-dev@groups.riscv.org,
	Gurucharan Kaur Saluja <gurucharankaurs@gmail.com>
Subject: RISCV64 SoC Architecture diagram
Date: Thu, 22 Nov 2018 13:04:03 +0530	[thread overview]
Message-ID: <CAOuPNLiQWiqwkhKXyKV08mWz-Zfis8O3dHB0W5UVfroLU=W4Rw@mail.gmail.com> (raw)
Message-ID: <20181122073403.i3245wklLxAU5qdumn9k9PlaQx61oGd8n0FSlbwlsks@z> (raw)

Hi All,

For the education purpose, we need RISCV SoC internal architecture
diagram which can give a pictorial overview of RISCV internals.
As part of study, we want to compare this with ARMv8 architecture.

If anybody have it please share.

Also, if anybody have risv64 benchmarking data with arm64, please
share this as well.


Thanks,
Pintu

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2018-11-22  7:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22  7:34 Pintu Agarwal [this message]
2018-11-22  7:34 ` RISCV64 SoC Architecture diagram Pintu Agarwal

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='CAOuPNLiQWiqwkhKXyKV08mWz-Zfis8O3dHB0W5UVfroLU=W4Rw@mail.gmail.com' \
    --to=pintu.ping@gmail.com \
    --cc=linux-riscv@lists.infradead.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).