On 13-10-17 06:39 AM, Diego Sueiro wrote:
2013/10/17 Bruce Ashfield <bruce.ashfi...@gmail.com <mailto:bruce.ashfi...@gmail.com>> On Wed, Oct 16, 2013 at 2:19 PM, Diego Sueiro <diego.sue...@gmail.com <mailto:diego.sue...@gmail.com>> wrote: > Folks, > > Looking at log.do_unpack it shows: > > ... > NOTE: Unpacking > <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.8/beaglebone/defconfig > to > <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/ > ... > > NOTE: Unpacking > <...>/meta-mine/recipes-kernel/linux/linux-mainline-3.8/mine.patch to > <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/ > NOTE: Unpacking > <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.8/beaglebone/defconfig > to > <...>/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/linux-mainline/3.8.13-r23a/ > > > Note that it copies defconfig from meta-beagleboard and in the end, instead > copying mine, it is copying from meta-beagleboard again. > > My layer has the priority higher than meta-beagleboard. I can't get at my machines to test this myself (technically I'm still on vacation), but when you dump the bitbake environment, how many defconfig's show up in the SRC_URI ? It would be easy enough in your bbapend to simply call your defconfig something else (i.e. defconfig-mine) and override/append to kernel_do_configure() to simply copy yours over top of the .config, regardless of what the fetcher is doing with the SRC_URI. Bruce Bruce, Putting the following in my recipe did the trick: do_configure_prepend() { cp ${WORKDIR}/defconfig-mine ${WORKDIR}/defconfig } Now the .config is the same as my custom defconfig. But, this is a workaround, right?
I could be. Until we root cause the issue, I can't say for sure.
I expected to get this working "out-of-box".
Did you do a "bitbake -e <your kernel recipe>" ? and then look at the SRC_URI ? That will tell us if for some reason the beagle layer's defconfig is on there twice.
Why config fragments did not worked too?
recipes must inherit linux-yocto to get that support, since it is optional and not something we force on all kernel recipes. So if you want fragment support, creating your own kernel recipe, based on the one in the layers you are using, which inherits linux-yocto is one route to take. Bruce
-- *dS Diego Sueiro /*long live rock 'n roll*/ _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
