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 2/2] hw/riscv: allow ramfb on virt
Date: Wed, 3 Mar 2021 17:30:26 -0500 [thread overview]
Message-ID: <CAKmqyKOOR=Vhy5EZ6L-T+6fd7_bF0W3ik1djHg2oGz9gQLUtbA@mail.gmail.com> (raw)
In-Reply-To: <20210228111657.23240-3-ashe@kivikakk.ee>
On Sun, Feb 28, 2021 at 6:20 AM Asherah Connor <ashe@kivikakk.ee> wrote:
>
> Allow ramfb on virt. This lets `-device ramfb' work.
>
> Signed-off-by: Asherah Connor <ashe@kivikakk.ee>
> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Alistair
>
> ---
>
> (no changes since v2)
>
> Changes in v2:
> * Add ramfb as allowed on riscv virt machine class.
>
> hw/riscv/virt.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/hw/riscv/virt.c b/hw/riscv/virt.c
> index 82eff42c37..700b481fa2 100644
> --- a/hw/riscv/virt.c
> +++ b/hw/riscv/virt.c
> @@ -42,6 +42,7 @@
> #include "sysemu/sysemu.h"
> #include "hw/pci/pci.h"
> #include "hw/pci-host/gpex.h"
> +#include "hw/display/ramfb.h"
>
> static const struct MemmapEntry {
> hwaddr base;
> @@ -743,6 +744,8 @@ static void virt_machine_class_init(ObjectClass *oc, void *data)
> mc->cpu_index_to_instance_props = riscv_numa_cpu_index_to_props;
> mc->get_default_cpu_node_id = riscv_numa_get_default_cpu_node_id;
> mc->numa_mem_supported = true;
> +
> + machine_class_allow_dynamic_sysbus_dev(mc, TYPE_RAMFB_DEVICE);
> }
>
> static const TypeInfo virt_machine_typeinfo = {
> --
> 2.20.1
>
>
next prev parent reply other threads:[~2021-03-03 22:33 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
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 [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='CAKmqyKOOR=Vhy5EZ6L-T+6fd7_bF0W3ik1djHg2oGz9gQLUtbA@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 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).