Messages in this thread | ![/](/images/icornerl.gif) | | Date | Thu, 29 Feb 2024 21:45:40 +0000 | From | Mark Brown <> | Subject | Re: [PATCH v8 33/38] kselftest/arm64: Add a GCS test program built with the system libc |
| |
On Thu, Feb 22, 2024 at 11:24:59PM -0300, Thiago Jung Bauermann wrote: > Mark Brown <broonie@kernel.org> writes:
> > I believe based on prior discussions that you're running this using > > shrinkwrap - can you confirm exactly how please, including things like > > which firmware configuration you're using? I'm using current git with > > > > shrinkwrap run \ > > --rtvar KERNEL=arch/arm64/boot/Image \ > > --rtvar ROOTFS=${ROOTFS} \ > > --rtvar CMDLINE="${CMDLINE}" \ > > --overlay=arch/v9.4.yaml ns-edk2.yaml > > > > and a locally built yocto and everything seems perfectly happy. > > Yes, this is how I'm running it: > > CMDLINE="Image dtb=fdt.dtb console=ttyAMA0 earlycon=pl011,0x1c090000 root=/dev/vda2 ip=dhcp maxcpus=1" > > shrinkwrap run \ > --rtvar=KERNEL=Image-gcs-v8-v6.7-rc4-14743-ga551a7d7af93 \
I guess that's bitrotted?
> My rootfs is Ubuntu 22.04.3. In case it's useful, my kernel config is > here:
...
> https://people.linaro.org/~thiago.bauermann/gcs/config-v6.8.0-rc2
Thanks, it seems to be something in your config that's making a difference - I can see issues with that. Hopefully that'll help me get to the bottom of this quickly. I spent a bunch of time fighting with Ubuntu images to get them running but once I did they didn't seem to make much difference. [unhandled content-type:application/pgp-signature] | ![\](/images/icornerr.gif) |