From: Peter Xu <peterx@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org,
thuth@redhat.com, cohuck@redhat.com,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] Kconfig: add documentation
Date: Wed, 13 Feb 2019 10:53:00 +0800 [thread overview]
Message-ID: <20190213025300.GB11247@xz-x1> (raw)
In-Reply-To: <20190212095749.20313-1-pbonzini@redhat.com>
On Tue, Feb 12, 2019 at 10:57:49AM +0100, Paolo Bonzini wrote:
[...]
> +Writing and modifying default configurations
> +--------------------------------------------
> +
> +In addition to the Kconfig files under hw/, each target also includes
> +a file called ``default-configs/TARGETNAME-softmmu.mak``. These files
> +initialize some Kconfig variables to non-default values and provide the
> +starting point to turn on devices and subsystems.
> +
> +A file in ``default-configs/`` looks like the following example::
> +
> + # Default configuration for alpha-softmmu
> +
> + # Uncomment the following lines to disable these optional devices:
> + #
> + #CONFIG_PCI_DEVICES=n
> + #CONFIG_TEST_DEVICES=n
> +
> + # Boards:
> + #
> + CONFIG_DP264=y
> +
> +The first part, consisting of commented-out ``=n`` assignments, tells
> +the user which devices or device groups are implied by the boards.
> +The second part, consisting of ``=y`` assignments, tells the user which
> +boards are supported by the target. The user will typically modify
> +default the configuration by uncommenting lines in the first group,
(noticed a trivial typo when read...)
s/default the/the default/
--
Peter Xu
prev parent reply other threads:[~2019-02-13 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 9:57 [Qemu-devel] [PATCH v2] Kconfig: add documentation Paolo Bonzini
2019-02-12 10:28 ` Cornelia Huck
2019-02-12 11:11 ` Liam Merwick
2019-02-13 2:53 ` Peter Xu [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=20190213025300.GB11247@xz-x1 \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=cohuck@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).