From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@lists.yoctoproject.org
Subject: Re: [poky] [PATCH] genericarm64.conf: fix qemu testing with testimage.bbclass
Date: Wed, 11 Mar 2026 14:18:46 +0200 [thread overview]
Message-ID: <abFdptsKldiqe76d@nuoska> (raw)
In-Reply-To: <2559713e813caeb132236d19744e3eba5b41728c.camel@linuxfoundation.org>
Hi,
On Wed, Mar 11, 2026 at 12:13:44PM +0000, Richard Purdie wrote:
> On Wed, 2026-03-11 at 14:10 +0200, Mikko Rapeli wrote:
> > > slirp, is a preference thing and I'd like to stay consistent
> > > between
> > > the qemu setups. It is not the default.
> >
> > It is the default on all builds and configuration I use and on meta-
> > arm so I would rather set this by default for genericarm64. Since
> > yocto upstream does not test genericarm64 I think this should be the
> > default.
>
> I don't, sorry.
>
> I've made my views on slirp and various other aspects of this clear
> multiple times. I'm wading into this again.
Understood. Are there some current issues with slirp in oeqa
selftests like runqemu, runtime_test, sdk or uki?
These are testing that slirp networking continues to work and AFAIK
there have not been issues with the tests lately on any qemu machines
tested on oe-core autobuilders.
Sad but I will drop this in v2.
Cheers,
-Mikko
prev parent reply other threads:[~2026-03-11 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 11:36 [PATCH] genericarm64.conf: fix qemu testing with testimage.bbclass Mikko Rapeli
2026-03-11 11:53 ` [poky] " Richard Purdie
2026-03-11 12:10 ` Mikko Rapeli
2026-03-11 12:13 ` Richard Purdie
2026-03-11 12:18 ` Mikko Rapeli [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=abFdptsKldiqe76d@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=poky@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.