How does a yocto bsp layer choose the defconfig?
Even in the examples or the documentation, the flow is not clear and I have no variable to actually change the defconfig file.
Nowhere in the linux recipe do I find the mention of the file defconfig for for that matter ARCH.
So here is my question, In case of a standalone kernel we have to do:
ARCH=arm64 CROSS_COMPILE=arm-linux-gnueabihf- make defconfig
How is this provided in yocto bsp layer?
Even when I consider, the poky/meta-yocto-bsp and poky/meta-skeleton, I do not see ARCH specification. How do you specify the layer to compile kernel for arm64 defconfig?
How does a yocto bsp layer choose the defconfig?
Even in the examples or the documentation, the flow is not clear and I have no variable to actually change the defconfig file.
Nowhere in the linux recipe do I find the mention of the file defconfig for for that matter ARCH.
So here is my question, In case of a standalone kernel we have to do:
ARCH=arm64 CROSS_COMPILE=arm-linux-gnueabihf- make defconfig
How is this provided in yocto bsp layer?
Even when I consider, the poky/meta-yocto-bsp and poky/meta-skeleton, I do not see ARCH specification. How do you specify witin the layer to compile kernel for arm64 defconfig?
To be clear, I am not talking about config fragments. I am talking about the primary defconfig itself.