From: Vijai Kumar K <vijai@behindbytes.com>
To: qemu-riscv@nongnu.org
Cc: Vijai Kumar K <vijai@behindbytes.com>, qemu-devel@nongnu.org
Subject: [PATCH 0/3] Add support for Shakti SoC from IIT-M
Date: Sun, 14 Mar 2021 14:09:33 +0530 [thread overview]
Message-ID: <20210314083936.76269-1-vijai@behindbytes.com> (raw)
This series adds initial suppport for emulating shakti soc[1] running
on arty 100T.
Shakti SoC uses Shakti C class core[2] and Shakti Uart[3]
[1] https://gitlab.com/shaktiproject/cores/shakti-soc/-/blob/master/README.rst
[2] https://gitlab.com/shaktiproject/cores/c-class/-/blob/master/README.md
[3] https://gitlab.com/shaktiproject/uncore/devices/-/tree/master/uart_v2
Vijai Kumar K (3):
riscv: Add initial support for Shakti C class
hw/char: Add Shakti UART emulation
hw/riscv: Connect Shakti UART to Shakti platform
MAINTAINERS | 9 +
default-configs/devices/riscv64-softmmu.mak | 1 +
hw/char/meson.build | 1 +
hw/char/shakti_uart.c | 204 ++++++++++++++++++++
hw/char/trace-events | 4 +
hw/riscv/Kconfig | 10 +
hw/riscv/meson.build | 1 +
hw/riscv/shakti_c.c | 185 ++++++++++++++++++
include/hw/char/shakti_uart.h | 74 +++++++
include/hw/riscv/shakti_c.h | 76 ++++++++
target/riscv/cpu.c | 9 +
target/riscv/cpu.h | 1 +
12 files changed, 575 insertions(+)
create mode 100644 hw/char/shakti_uart.c
create mode 100644 hw/riscv/shakti_c.c
create mode 100644 include/hw/char/shakti_uart.h
create mode 100644 include/hw/riscv/shakti_c.h
--
2.25.1
next reply other threads:[~2021-03-14 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 8:39 Vijai Kumar K [this message]
2021-03-14 8:39 ` [PATCH 1/3] riscv: Add initial support for Shakti C class Vijai Kumar K
2021-03-19 13:39 ` Alistair Francis
2021-03-20 9:46 ` Vijai Kumar K
2021-03-14 8:39 ` [PATCH 2/3] hw/char: Add Shakti UART emulation Vijai Kumar K
2021-03-19 13:44 ` Alistair Francis
2021-03-20 9:41 ` Vijai Kumar K
2021-03-14 8:39 ` [PATCH 3/3] hw/riscv: Connect Shakti UART to Shakti platform Vijai Kumar K
2021-03-19 13:47 ` Alistair Francis
2021-03-20 9:38 ` Vijai Kumar K
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=20210314083936.76269-1-vijai@behindbytes.com \
--to=vijai@behindbytes.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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).