Hi meta-ti maintainers, We've hit an issue where selecting a BSP version (e.g. TI_PREFERRED_BSP = "mainline") also forces initramfs integration via ti-soc.inc (lines 32-49). The bsp-mainline, bsp-next, and bsp-ti_6_18 overrides all unconditionally set BUILD_CORE_INITRAMFS_IMAGE_STEP, TI_WKS_INITRAMFS, and IMAGE_BOOT_FILES.
This means we can't use bsp-mainline without also pulling in ti-core-initramfs — even when our images don't need it. Since we can't use bsp-mainline, we also lose the correct override context for other components. For example, we end up having to manually override all the mesa-pvr.inc virtual providers in our machine config to use upstream mesa — something that bsp-mainline would handle naturally. The root issue is that initramfs integration (an image-level concern) is tied to BSP version selection (a machine-level concern) in ti-soc.inc. A possible fix would be to move the initramfs logic to an image class (e.g. ti- image.bbclass) that images explicitly opt into. This would be a breaking change for images relying on the current automatic behavior, but it would properly separate these concerns. Would this approach be welcome? We're happy to contribute patches. Best regards, Vitor Soares Toradex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19472): https://lists.yoctoproject.org/g/meta-ti/message/19472 Mute This Topic: https://lists.yoctoproject.org/mt/117717310/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
