[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] QEMU and Kconfig
From: |
Peter Maydell |
Subject: |
Re: [Qemu-devel] QEMU and Kconfig |
Date: |
Wed, 26 Sep 2018 20:57:55 +0100 |
On 26 September 2018 at 14:36, Paolo Bonzini <address@hidden> wrote:
> Here is a minimal example:
>
> # hw/scsi/Kconfig
> config SCSI
>
> config ESP
> select SCSI
>
> config ESP_PCI
> default y
> select ESP
> depends on PCI
>
> # hw/pci/Kconfig
> config PCI
>
> # hw/pci-host/Kconfig
> config PCI_GENERIC
> select PCI
>
> # hw/arm/Kconfig
> config ARM_VIRT
> select PCI_GENERIC
> default y
>
> # hw/sparc/Kconfig
> config SUN4M
> select ESP
> default y
What is the syntactic thing in this example which distinguishes
"user can toggle this" (ESP_PCI, ARM_VIRT, SUN4M) from "user
can't toggle this, it's just an internal thing selected by
other nodes" (the rest) ? I'm assuming we'd have some sort
of UI thingy that presents the user only with the user-settable
options.
thanks
-- PMM
- [Qemu-devel] QEMU and Kconfig, Samuel Ortiz, 2018/09/24
- Re: [Qemu-devel] QEMU and Kconfig, Thomas Huth, 2018/09/25
- Re: [Qemu-devel] QEMU and Kconfig, Paolo Bonzini, 2018/09/25
- Re: [Qemu-devel] QEMU and Kconfig, Samuel Ortiz, 2018/09/26
- Re: [Qemu-devel] QEMU and Kconfig, Peter Maydell, 2018/09/26
- Re: [Qemu-devel] QEMU and Kconfig, Paolo Bonzini, 2018/09/26
- Re: [Qemu-devel] QEMU and Kconfig, Samuel Ortiz, 2018/09/26
- Re: [Qemu-devel] QEMU and Kconfig, Paolo Bonzini, 2018/09/26
- Re: [Qemu-devel] QEMU and Kconfig,
Peter Maydell <=
- Re: [Qemu-devel] QEMU and Kconfig, Paolo Bonzini, 2018/09/27