From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: docs@lists.yoctoproject.org
Subject: Re: [docs] qemuboot.conf variables
Date: Mon, 17 Feb 2025 15:37:43 -0600 [thread overview]
Message-ID: <4a3d8dbb-e8f7-43af-a61b-c8b6edbc635e@kernel.crashing.org> (raw)
In-Reply-To: <7cc39a0b-9a11-4716-97a4-985bdc885b0e@cherry.de>
On 2/17/25 6:04 AM, Quentin Schulz via lists.yoctoproject.org wrote:
> Hi Mark,
>
> On 2/14/25 4:50 PM, Mark Hatle via lists.yoctoproject.org wrote:
>> When I was looking through the large docs, I didn't see anything inside
>> of it to explain the various variables used in the qemuboot.conf file.
>>
>> Looking through the code, I found the stuff mostly in the class that
>> creates the file, but there were also fragments of explanation in prior
>> commit messages and other places. Below is my attempt to collect all of
>> the qemuboot.conf variables in one place, along with an explanation. I
>> think this would be useful to add to the regular docs, but I'm not
>> exactly sure where or what format.
>>
>
> We do have a QEMU-specific document so that could be a start though we
> don't have a glossary in there so we wouldn't be able to :term:`QB_DTB`
> for example elsewhere in the docs.
>
> Another option is to have them all in the variables glossary with other
> variables. They may be a bit too machine-specific to be there, but maybe
> that's fine. In short, I don't know either what would be best. We could
> start with documentation/dev-manual/qemu.rst in any case.
I think a qemu specific document or section would be my suggested. There is a
lot of stuff about runqemu that is documented in the code or in random places
and it would be nice to move it all to one place.
>> There are some other things related to runqemu usage that would be nice
>> to document as well (command line usage, environment variable, command
>
> We do have a section on the command line options for runqemu, are you
> thinking about something different?
This is only a small part. There are environment variables and how they are
used, substitutions such as @PORT@ and others that are applied to certain parts
of the configuration, etc. Each of these really should be documented.
>> substitution behavior and generated command line rules), but the items
>> below are the ones that I had to search for when I was trying to explain
>> the qemuboot.conf to someone else.
>>
>
> Thanks for sharing the info with us, looking forward to having patches
> on the mailing list :)
>
> Cheers,
> Quentin
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#6382): https://lists.yoctoproject.org/g/docs/message/6382
> Mute This Topic: https://lists.yoctoproject.org/mt/111184281/3616948
> Group Owner: docs+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/docs/unsub [mark.hatle@kernel.crashing.org]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2025-02-17 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 15:50 qemuboot.conf variables Mark Hatle
2025-02-17 12:04 ` [docs] " Quentin Schulz
2025-02-17 21:37 ` Mark Hatle [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=4a3d8dbb-e8f7-43af-a61b-c8b6edbc635e@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=docs@lists.yoctoproject.org \
/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