All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Cc: "Aleksandar Rikalo" <arikalo@wavecomp.com>,
	"Aleksandar Markovic" <amarkovic@wavecomp.com>,
	"James Hogan" <jhogan@kernel.org>,
	"Aurelien Jarno" <aurelien@aurel32.net>,
	"Yang Zhong" <yang.zhong@intel.com>,
	"Paul Burton" <pburton@wavecomp.com>,
	"Hervé Poussineau" <hpoussin@reactos.org>
Subject: Re: [Qemu-devel] [PATCH 0/6] Kconfig dependencies for MIPS machines (but Malta)
Date: Mon, 4 Feb 2019 12:19:43 +0100	[thread overview]
Message-ID: <497c12d9-37e5-7bcf-caf7-d58f0b72d2ad@redhat.com> (raw)
In-Reply-To: <203ecbc6-b82b-9d55-9919-36c4a8023882@redhat.com>

On 04/02/19 10:51, Thomas Huth wrote:
> On 2019-02-04 01:06, Philippe Mathieu-Daudé wrote:
>> On Sun, Feb 3, 2019 at 11:07 PM Philippe Mathieu-Daudé
>> <philmd@redhat.com> wrote:
>>>
>>> Express the MIPS machine dependencies with Kconfig.
>>
>> I forgot this serie misses a rule such "depends of MIPS64".
>> Asked here: https://lists.gnu.org/archive/html/qemu-devel/2019-02/msg00064.html
> 
> I guess the easiest solution is to simply set a CONFIG_MIPS64=y in the
> default-configs/mips64*softmmu* files.

Or just do not specify the machine in the mips64*softmmu.mak files.  If
you add CONFIG_Q35=y to ARM, Kconfig doesn't complain.

Another possibility is to move those machines to hw/mips64, similar to
hw/sparc64.

Paolo

      reply	other threads:[~2019-02-04 11:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 22:07 [Qemu-devel] [PATCH 0/6] Kconfig dependencies for MIPS machines (but Malta) Philippe Mathieu-Daudé
2019-02-03 22:07 ` [Qemu-devel] [PATCH 1/6] mips: Express dependencies of the MIPSsim machine with kconfig Philippe Mathieu-Daudé
2019-02-04  8:31   ` Thomas Huth
2019-02-04  8:36     ` Thomas Huth
2019-02-04 11:05       ` Philippe Mathieu-Daudé
2019-02-04 11:21         ` Paolo Bonzini
2019-02-04 11:55           ` Philippe Mathieu-Daudé
2019-02-03 22:07 ` [Qemu-devel] [PATCH 2/6] mips: Express dependencies of the Jazz " Philippe Mathieu-Daudé
2019-02-04  8:36   ` Thomas Huth
2019-02-03 22:07 ` [Qemu-devel] [PATCH 3/6] mips: Express dependencies of the r4k platform " Philippe Mathieu-Daudé
2019-02-04  8:39   ` Thomas Huth
2019-02-03 22:07 ` [Qemu-devel] [PATCH 4/6] mips: Express dependencies of the Boston machine " Philippe Mathieu-Daudé
2019-02-03 22:07 ` [Qemu-devel] [PATCH 5/6] hw/pci-host: Use CONFIG_PCI_BONITO to select the Bonito North Bridge Philippe Mathieu-Daudé
2019-02-04  8:40   ` Thomas Huth
2019-02-03 22:07 ` [Qemu-devel] [PATCH 6/6] mips: Express dependencies of the Loongson 2E machine with kconfig Philippe Mathieu-Daudé
2019-02-04  8:46   ` Thomas Huth
2019-02-04 20:16     ` Philippe Mathieu-Daudé
2019-02-04  0:06 ` [Qemu-devel] [PATCH 0/6] Kconfig dependencies for MIPS machines (but Malta) Philippe Mathieu-Daudé
2019-02-04  9:51   ` Thomas Huth
2019-02-04 11:19     ` Paolo Bonzini [this message]

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=497c12d9-37e5-7bcf-caf7-d58f0b72d2ad@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=amarkovic@wavecomp.com \
    --cc=arikalo@wavecomp.com \
    --cc=aurelien@aurel32.net \
    --cc=hpoussin@reactos.org \
    --cc=jhogan@kernel.org \
    --cc=pburton@wavecomp.com \
    --cc=philmd@redhat.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 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.