Re: [yocto] [PATCH v7 0/7] Add barebox bootloader support (and testing)

[Ahmad Fatoum <a.fatoum@pengutronix.de>]

Hello Richard,

On 01.10.24 16:56, Richard Purdie wrote:
> On Tue, 2024-10-01 at 16:35 +0200, Ahmad Fatoum wrote:
>> My successful run looks identical to yours. barebox start up is also
>> successful and uneventful.
>>
>> Note that barebox' XHCI driver doesn't have PCI support unlike U-Boot, so
>> if the same issue is affecting both barebox and U-Boot breakage in CI,
>> it might not be USB emulation related as barebox doesn't do any
>> USB on that platform...
>>
>> Is `selftest -r uboot -v -v -v -K` close enough to what the CI server runs
>> or should I try something else to reproduce this?
> 
> That should have worked. "selftest -r barebox" should also fail.
> 
> The config used on the autobuilder for that can be seen here:
> 
> https://valkyrie.yoctoproject.org/#/builders/23/builds/168/steps/13/logs/stdio
> 
> in case the MACHINE value in particular makes a difference.

I am building for MACHINE = "qemuarm64" already, but something else catches
my eye: QEMU_USE_KVM = 'True'

I wasn't aware that I need to manually set this. I do this now and it fails
for other reasons: qemu-system-aarch64: KVM does not support GICv3 emulation

I'll look into how to resolve this and maybe I am lucky and can reproduce
this issue, once KVM is enabled.

Can you share what SoC is used for the ARM CI server? I assume it doesn't
run into this problem, because it has a GIC >= v3. Mine is a GIC-400,
which apparently only implements GICv2.

Cheers,
Ahmad

> 
> Cheers,
> 
> Richard
> 
> 
> 


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |