You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, meta-virtualization coerces raspberrypi4-64 builds to use the linux-yocto recipe. However, the bcm-2xxx-rpi4 kmeta from yocto-kernel-cache depends on a whole heap of CONFIGs only present in the downstream Linux repository at github.com/raspberrypi/linux. Therefore, you end up with several kconfig warnings for missing CONFIGs. We should just let meta-raspberrypi use its own Linux recipe as it plays nicely with kmeta now anyway.
The text was updated successfully, but these errors were encountered:
At the moment, meta-virtualization coerces raspberrypi4-64 builds to use the
linux-yocto
recipe. However, the bcm-2xxx-rpi4 kmeta fromyocto-kernel-cache
depends on a whole heap of CONFIGs only present in the downstream Linux repository at github.com/raspberrypi/linux. Therefore, you end up with several kconfig warnings for missing CONFIGs. We should just let meta-raspberrypi use its own Linux recipe as it plays nicely with kmeta now anyway.The text was updated successfully, but these errors were encountered: