From: Palmer Dabbelt <palmerdabbelt@google.com>
To: Anup Patel <Anup.Patel@wdc.com>
Cc: palmer@sifive.com, anup@brainfault.org,
Anup Patel <Anup.Patel@wdc.com>,
linux-kernel@vger.kernel.org, Atish Patra <Atish.Patra@wdc.com>,
aou@eecs.berkeley.edu,
Alistair Francis <Alistair.Francis@wdc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/4] RISC-V: Add kconfig option for QEMU virt machine
Date: Mon, 02 Dec 2019 15:32:49 -0800 (PST) [thread overview]
Message-ID: <mhng-db354582-74fd-45db-974e-3cece2ad6ab2@palmerdabbelt.mtv.corp.google.com> (raw)
In-Reply-To: <20191125132147.97111-2-anup.patel@wdc.com>
On Mon, 25 Nov 2019 05:22:23 PST (-0800), Anup Patel wrote:
> We add kconfig option for QEMU virt machine and select all
> required VIRTIO drivers using this kconfig option.
>
> Signed-off-by: Anup Patel <anup.patel@wdc.com>
> ---
> arch/riscv/Kconfig.socs | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/arch/riscv/Kconfig.socs b/arch/riscv/Kconfig.socs
> index 536c0ef4aee8..62383951bf2e 100644
> --- a/arch/riscv/Kconfig.socs
> +++ b/arch/riscv/Kconfig.socs
> @@ -10,4 +10,24 @@ config SOC_SIFIVE
> help
> This enables support for SiFive SoC platform hardware.
>
> +config SOC_VIRT
> + bool "QEMU Virt Machine"
> + select VIRTIO_PCI
> + select VIRTIO_BALLOON
> + select VIRTIO_MMIO
> + select VIRTIO_CONSOLE
> + select VIRTIO_NET
> + select NET_9P_VIRTIO
> + select VIRTIO_BLK
> + select SCSI_VIRTIO
> + select DRM_VIRTIO_GPU
> + select HW_RANDOM_VIRTIO
> + select RPMSG_CHAR
> + select RPMSG_VIRTIO
> + select CRYPTO_DEV_VIRTIO
> + select VIRTIO_INPUT
> + select SIFIVE_PLIC
> + help
> + This enables support for QEMU Virt Machine.
> +
> endmenu
Reviewed-by: Palmer Dabbelt <palmerdabbelt@google.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-12-02 23:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 13:22 [PATCH 0/4] QEMU Virt Machine Kconfig option Anup Patel
2019-11-25 13:22 ` [PATCH 1/4] RISC-V: Add kconfig option for QEMU virt machine Anup Patel
2019-11-26 19:12 ` Atish Patra
2019-12-02 23:32 ` Palmer Dabbelt [this message]
2020-03-09 10:11 ` Andreas Schwab
2020-03-09 10:24 ` Anup Patel
2020-03-10 10:21 ` Andreas Schwab
2020-03-10 11:57 ` Anup Patel
2019-11-25 13:22 ` [PATCH 2/4] RISC-V: Enable QEMU virt machine support in defconfigs Anup Patel
2019-11-26 19:14 ` Atish Patra
2019-12-02 23:32 ` Palmer Dabbelt
2019-12-03 3:06 ` Anup Patel
2019-11-25 13:22 ` [PATCH 3/4] RISC-V: Select SYSCON Reboot and Poweroff for QEMU virt machine Anup Patel
2019-12-02 23:32 ` Palmer Dabbelt
2019-11-25 13:22 ` [PATCH 4/4] RISC-V: Select Goldfish RTC driver " Anup Patel
2019-11-26 19:17 ` Atish Patra
2019-12-02 23:32 ` Palmer Dabbelt
2019-12-02 23:32 ` [PATCH 0/4] QEMU Virt Machine Kconfig option Palmer Dabbelt
2019-12-03 3:03 ` Anup Patel
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=mhng-db354582-74fd-45db-974e-3cece2ad6ab2@palmerdabbelt.mtv.corp.google.com \
--to=palmerdabbelt@google.com \
--cc=Alistair.Francis@wdc.com \
--cc=Anup.Patel@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
/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).