Re: [PATCH v4 2/4] qemuarm64.conf: allow overriding QB_OPT_APPEND

[Tom Rini <trini@konsulko.com>]

[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]

On Wed, May 28, 2025 at 11:02:44AM +0300, Mikko Rapeli wrote:
> Hi,
> 
> On Tue, May 27, 2025 at 06:52:47PM -0600, Tom Rini wrote:
> > On Mon, May 26, 2025 at 11:35:45AM +0300, Mikko Rapeli wrote:
> > 
> > > It enables qemu USB support which causes a reset
> > > loop currently with u-boot.
> > > 
> > > Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> > > ---
> > >  meta/conf/machine/qemuarm64.conf | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > This too feel like something that should be brought up on the U-Boot
> > side.
> 
> We saw these issues in 2023 on qemu but thought they were specific to our
> Trusted Substrate config with tf-a, OP-TEE and u-boot. Some public info is
> in: https://linaro.atlassian.net/browse/LEDGE-435
> 
> I know USB support is really tricky with timings etc so I don't expect
> it to work well with bootloaders. Hence did not dig deeper.
> 
> Now that I saw this reset loop with KVM I will note the details down
> with reproduction steps and send to u-boot list.
> 
> But I think overriding QB_OPT_APPEND is handy, wether it has USB setup
> or something else. Other layers in yocto ecosystem use qemuarm64 as basis
> machine with testing and may want to change this.

I would say there are two parts to this. On the U-Boot side, USB is
expected to work and we have active custodians dealing with it. Please
work with Ilias and others to get a reproduceable set of steps with
vanilla QEMU and report them to the U-Boot list with appropriate CC. On
the OE side, it's all complicated enough that I would defer to Richard.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]