From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-trivial] [PATCH] docs/devel/build-system: Update an example
Date: Wed, 15 May 2019 09:21:39 +0200 [thread overview]
Message-ID: <b9ca67e7-e9d4-0f7c-1ec6-166643d4c5cb@redhat.com> (raw)
In-Reply-To: <552b024d-39bd-dd3f-bf44-3c3e0a9f1198@redhat.com>
On 5/15/19 9:16 AM, Thomas Huth wrote:
> On 15/05/2019 09.03, Philippe Mathieu-Daudé wrote:
>> The default-configs/ example added in 717171bd2025 is no
>> more accurate since fa212a2b8b60 (and various further other
>> commits).
>>
>> The Kconfig build system is now in place.
>> Use the aarch64-softmmu config as example.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> ---
>> docs/devel/build-system.txt | 15 +++++----------
>> 1 file changed, 5 insertions(+), 10 deletions(-)
>>
>> diff --git a/docs/devel/build-system.txt b/docs/devel/build-system.txt
>> index addd274eebd..79a85bfba06 100644
>> --- a/docs/devel/build-system.txt
>> +++ b/docs/devel/build-system.txt
>> @@ -415,16 +415,11 @@ context.
>> The files under default-configs/ control what emulated hardware is built
>> into each QEMU system and userspace emulator targets. They merely
>> contain a long list of config variable definitions. For example,
>
> "long list" is now often also not very accurate anymore. Maybe rephrase
Still accurate for MIPS :(
> that sentence à la: "contain a list of config variable definitions like
> the machines that should be included" ?
Good idea.
>
>> -default-configs/x86_64-softmmu.mak has:
>> -
>> - include sound.mak
>> - include usb.mak
>> - CONFIG_QXL=$(CONFIG_SPICE)
>> - CONFIG_VGA_ISA=y
>> - CONFIG_VGA_CIRRUS=y
>> - CONFIG_VMWARE_VGA=y
>> - CONFIG_VIRTIO_VGA=y
>> - ...snip...
>> +default-configs/aarch64-softmmu.mak has:
>> +
>> + include arm-softmmu.mak
>> + CONFIG_XLNX_ZYNQMP_ARM=y
>> + CONFIG_XLNX_VERSAL=y
>>
>> These files rarely need changing unless new devices / hardware need to
>> be enabled for a particular system/userspace emulation target
>>
>
> Anyway,
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
>
Thanks!
Phil.
prev parent reply other threads:[~2019-05-15 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 7:03 [Qemu-trivial] [PATCH] docs/devel/build-system: Update an example Philippe Mathieu-Daudé
2019-05-15 7:16 ` Thomas Huth
2019-05-15 7:21 ` Philippe Mathieu-Daudé [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=b9ca67e7-e9d4-0f7c-1ec6-166643d4c5cb@redhat.com \
--to=philmd@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.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).