Message ID | 20190203220744.11734-1-philmd@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | Kconfig dependencies for MIPS machines (but Malta) | expand |
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
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. Thomas
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