From: Bin Meng <bmeng.cn@gmail.com>
To: Asherah Connor <ashe@kivikakk.ee>
Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <Alistair.Francis@wdc.com>
Subject: Re: [PATCH v3 1/2] hw/riscv: Add fw_cfg support to virt
Date: Sun, 28 Feb 2021 19:44:28 +0800 [thread overview]
Message-ID: <CAEUhbmXPC5CKnsvx7_0qG4eN3zMS6as4PkbxSE-kv0De1Lv_VQ@mail.gmail.com> (raw)
In-Reply-To: <20210228111657.23240-2-ashe@kivikakk.ee>
On Sun, Feb 28, 2021 at 7:17 PM Asherah Connor <ashe@kivikakk.ee> wrote:
>
> Provides fw_cfg for the virt machine on riscv. This enables
> using e.g. ramfb later.
>
> Signed-off-by: Asherah Connor <ashe@kivikakk.ee>
> ---
>
> Changes in v3:
> * Document why fw_cfg is done when it is.
> * Move VIRT_FW_CFG before VIRT_FLASH.
>
> Changes in v2:
> * Add DMA support (needed for writes).
>
> hw/riscv/Kconfig | 1 +
> hw/riscv/virt.c | 30 ++++++++++++++++++++++++++++++
> include/hw/riscv/virt.h | 2 ++
> 3 files changed, 33 insertions(+)
>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
next prev parent reply other threads:[~2021-02-28 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 11:16 [PATCH v3 0/2] hw/riscv: Add fw_cfg support, allow ramfb Asherah Connor
2021-02-28 11:16 ` [PATCH v3 1/2] hw/riscv: Add fw_cfg support to virt Asherah Connor
2021-02-28 11:44 ` Bin Meng [this message]
2021-03-03 22:33 ` Alistair Francis
2021-03-18 21:25 ` Alistair Francis
2021-03-18 21:28 ` Alistair Francis
2021-03-18 23:24 ` Asherah Connor
2021-02-28 11:16 ` [PATCH v3 2/2] hw/riscv: allow ramfb on virt Asherah Connor
2021-03-03 22:30 ` Alistair Francis
2021-03-03 22:50 ` [PATCH v3 0/2] hw/riscv: Add fw_cfg support, allow ramfb Alistair Francis
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=CAEUhbmXPC5CKnsvx7_0qG4eN3zMS6as4PkbxSE-kv0De1Lv_VQ@mail.gmail.com \
--to=bmeng.cn@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=ashe@kivikakk.ee \
--cc=kbastian@mail.uni-paderborn.de \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).