From: Alistair Francis <alistair23@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>,
Alistair Francis <Alistair.Francis@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Bin Meng <bmeng.cn@gmail.com>
Subject: Re: [PATCH v3 0/2] hw/riscv: Add fw_cfg support, allow ramfb
Date: Wed, 3 Mar 2021 17:50:52 -0500 [thread overview]
Message-ID: <CAKmqyKMv-TBYAK2kEEBmZ8J10iDk86YoNa=Pkpj-fmZAKa9+7A@mail.gmail.com> (raw)
In-Reply-To: <20210228111657.23240-1-ashe@kivikakk.ee>
On Sun, Feb 28, 2021 at 6:18 AM Asherah Connor <ashe@kivikakk.ee> wrote:
>
> This is version 3 of the series to bring fw_cfg support to riscv's virt
> machine, including ramfb support. It is tested as working against a
> modified U-Boot with ramfb support.
Thanks!
Applied to riscv-to-apply.next
Alistair
>
>
> 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).
> * Add ramfb as allowed on riscv virt machine class.
>
> Asherah Connor (2):
> hw/riscv: Add fw_cfg support to virt
> hw/riscv: allow ramfb on virt
>
> hw/riscv/Kconfig | 1 +
> hw/riscv/virt.c | 33 +++++++++++++++++++++++++++++++++
> include/hw/riscv/virt.h | 2 ++
> 3 files changed, 36 insertions(+)
>
> --
> 2.20.1
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Alistair Francis <alistair23@gmail.com>
To: Asherah Connor <ashe@kivikakk.ee>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"open list:RISC-V" <qemu-riscv@nongnu.org>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Alistair Francis <Alistair.Francis@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Bin Meng <bmeng.cn@gmail.com>
Subject: Re: [PATCH v3 0/2] hw/riscv: Add fw_cfg support, allow ramfb
Date: Wed, 3 Mar 2021 17:50:52 -0500 [thread overview]
Message-ID: <CAKmqyKMv-TBYAK2kEEBmZ8J10iDk86YoNa=Pkpj-fmZAKa9+7A@mail.gmail.com> (raw)
In-Reply-To: <20210228111657.23240-1-ashe@kivikakk.ee>
On Sun, Feb 28, 2021 at 6:18 AM Asherah Connor <ashe@kivikakk.ee> wrote:
>
> This is version 3 of the series to bring fw_cfg support to riscv's virt
> machine, including ramfb support. It is tested as working against a
> modified U-Boot with ramfb support.
Thanks!
Applied to riscv-to-apply.next
Alistair
>
>
> 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).
> * Add ramfb as allowed on riscv virt machine class.
>
> Asherah Connor (2):
> hw/riscv: Add fw_cfg support to virt
> hw/riscv: allow ramfb on virt
>
> hw/riscv/Kconfig | 1 +
> hw/riscv/virt.c | 33 +++++++++++++++++++++++++++++++++
> include/hw/riscv/virt.h | 2 ++
> 3 files changed, 36 insertions(+)
>
> --
> 2.20.1
>
>
next prev parent reply other threads:[~2021-03-03 22:52 UTC|newest]
Thread overview: 20+ 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 ` 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:16 ` Asherah Connor
2021-02-28 11:44 ` Bin Meng
2021-02-28 11:44 ` Bin Meng
2021-03-03 22:33 ` Alistair Francis
2021-03-03 22:33 ` Alistair Francis
2021-03-18 21:25 ` Alistair Francis
2021-03-18 21:25 ` Alistair Francis
2021-03-18 21:28 ` Alistair Francis
2021-03-18 21:28 ` Alistair Francis
2021-03-18 23:24 ` Asherah Connor
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-02-28 11:16 ` Asherah Connor
2021-03-03 22:30 ` Alistair Francis
2021-03-03 22:30 ` Alistair Francis
2021-03-03 22:50 ` Alistair Francis [this message]
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='CAKmqyKMv-TBYAK2kEEBmZ8J10iDk86YoNa=Pkpj-fmZAKa9+7A@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=ashe@kivikakk.ee \
--cc=bmeng.cn@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.