From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Hervé Poussineau" <hpoussin@reactos.org>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Yang Zhong" <yang.zhong@intel.com>,
"Paul Burton" <pburton@wavecomp.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Aleksandar Rikalo" <arikalo@wavecomp.com>,
"James Hogan" <jhogan@kernel.org>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [Qemu-devel] [PATCH v2 4/6] mips: Express dependencies of the Boston machine with kconfig
Date: Mon, 4 Feb 2019 21:26:07 +0100 [thread overview]
Message-ID: <20190204202609.26956-5-philmd@redhat.com> (raw)
In-Reply-To: <20190204202609.26956-1-philmd@redhat.com>
Boston is built around a Xilinx FPGA, which includes a PCIe root port
and an UART. An Intel EG20T PCH connects the I/O peripherals, but only
the SATA bus is emulated.
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
---
default-configs/mips64el-softmmu.mak | 4 ----
hw/mips/Kconfig | 5 +++++
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/default-configs/mips64el-softmmu.mak b/default-configs/mips64el-softmmu.mak
index 23445cfcf9..c6f1f9c9aa 100644
--- a/default-configs/mips64el-softmmu.mak
+++ b/default-configs/mips64el-softmmu.mak
@@ -4,8 +4,4 @@ include mips-softmmu-common.mak
CONFIG_IDE_VIA=y
CONFIG_FULONG=y
CONFIG_VT82C686=y
-CONFIG_AHCI=y
CONFIG_MIPS_BOSTON=y
-CONFIG_FITLOADER=y
-CONFIG_PCI_EXPRESS=y
-CONFIG_PCI_EXPRESS_XILINX=y
diff --git a/hw/mips/Kconfig b/hw/mips/Kconfig
index ee6290d497..2940ff39ab 100644
--- a/hw/mips/Kconfig
+++ b/hw/mips/Kconfig
@@ -49,3 +49,8 @@ config MIPS_CPS
config MIPS_BOSTON
bool
+ select FITLOADER
+ select MIPS_CPS
+ select PCI_EXPRESS_XILINX
+ select AHCI
+ select SERIAL
--
2.20.1
next prev parent reply other threads:[~2019-02-04 20:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 20:26 [Qemu-devel] [PATCH v2 0/6] Kconfig dependencies for MIPS machines (but Malta) Philippe Mathieu-Daudé
2019-02-04 20:26 ` [Qemu-devel] [PATCH v2 1/6] mips: Express dependencies of the MIPSsim machine with kconfig Philippe Mathieu-Daudé
2019-02-05 3:35 ` Thomas Huth
2019-02-04 20:26 ` [Qemu-devel] [PATCH v2 2/6] mips: Express dependencies of the Jazz " Philippe Mathieu-Daudé
2019-02-05 4:04 ` Thomas Huth
2019-02-05 11:57 ` Philippe Mathieu-Daudé
2019-02-04 20:26 ` [Qemu-devel] [PATCH v2 3/6] mips: Express dependencies of the r4k platform " Philippe Mathieu-Daudé
2019-02-05 4:11 ` Thomas Huth
2019-02-05 11:58 ` Philippe Mathieu-Daudé
2019-02-04 20:26 ` Philippe Mathieu-Daudé [this message]
2019-02-05 4:13 ` [Qemu-devel] [PATCH v2 4/6] mips: Express dependencies of the Boston machine " Thomas Huth
2019-02-28 22:26 ` Paul Burton
2019-02-04 20:26 ` [Qemu-devel] [PATCH v2 5/6] hw/pci-host: Use CONFIG_PCI_BONITO to select the Bonito North Bridge Philippe Mathieu-Daudé
2019-02-04 20:26 ` [Qemu-devel] [PATCH v2 6/6] mips: Express dependencies of the Loongson 2E machine with kconfig Philippe Mathieu-Daudé
2019-02-05 12:18 ` Philippe Mathieu-Daudé
2019-02-19 17:54 ` Aleksandar Markovic
2019-02-19 19:07 ` Philippe Mathieu-Daudé
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=20190204202609.26956-5-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=amarkovic@wavecomp.com \
--cc=arikalo@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=hpoussin@reactos.org \
--cc=jhogan@kernel.org \
--cc=pbonzini@redhat.com \
--cc=pburton@wavecomp.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=yang.zhong@intel.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).