public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: docs@lists.yoctoproject.org
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Possible runqemu release note for Nanbield
Date: Wed, 25 Oct 2023 15:58:37 -0500	[thread overview]
Message-ID: <da900cde-800c-5b0e-80cb-199a93652b50@kernel.crashing.org> (raw)

While porting meta-xilinx to nanbield I ran into a difference with the way 
runqemu works.  I figure this might be something that should be a release note, 
but unfortunately I'm not sure I understand how to explain it well.  Below are 
my findings and maybe we can word-smith this into a proper release note.

In Mickledore and before 'runqemu' when run like:

runqemu nographic

would automatically add "-serial mon:stdio" after the QB_OPT_APPEND values as 
necessary.  (It might have also added "-serial null" in some cases, but after 
"-serial mon:stdio".). After the commit:

https://git.yoctoproject.org/poky/commit/?h=nanbield&id=8c4bb95c1c472f9eb5235b848e57febcac53aa59

This has changed to counting the number of serial ports and adding "-serial 
null" if the QB_OPT_APPEND only defined a single serial port, and if two or more 
ports are specified avoiding automatically adding -serial mon:stdio.  This can 
break some existing QEMU based configurations by changing the way the serial 
ports are automatically determined when runqemu is executed.

It may be necessary to compare a prior working (Mickledore) executing and 
adjusting QB_OPT_APPEND to include the correct ordering and number of serial 
ports of the emulated machine.



Hopefully Richard or someone can verify what I wrong about is accurate, and 
maybe adjust it to better explain how a user should adjust their BSP integration.

Thanks!

--Mark


             reply	other threads:[~2023-10-25 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 20:58 Mark Hatle [this message]
2023-10-26 15:59 ` [docs] Possible runqemu release note for Nanbield Michael Opdenacker
2023-10-26 17:23   ` Mark Hatle

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=da900cde-800c-5b0e-80cb-199a93652b50@kernel.crashing.org \
    --to=mark.hatle@kernel.crashing.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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