Diego, You are appending a kernel recipe that uses the Linux Yocto tooling. The defconfig is essentially comprised of many different pieces from the meta branch of the Yocto kernel repository and optional configuration fragments that you provide. This tooling will not recognize a defconfig file you provide but it does recognize configuration fragments to be added to .config.
You need to put CONFIG_WATCHDOG_NOWAYOUT=y into a file that ends with .cfg eg. watchdog.cfg and then modify your bbappend to FILESEXTRAPATHS_prepend := "${THISDIR}/files:" SRC_URI += " file://0019-mine.patch \ file://watchdog.cfg \ " Rudi On Tue, Oct 15, 2013 at 2:07 PM, Diego Sueiro <diego.sue...@gmail.com>wrote: > Folks, > > I created the following bbapend recipe for linux-mainline_3.8.bb (from > meta-beagleboard on dylan branch) for beaglebone. > meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend: > > FILESEXTRAPATHS_prepend := "${THISDIR}/files:" > SRC_URI += " file://0019-mine.patch \ > file://defconfig \ > " > > But the defconfig and .config files on ${S} and ${WORKDIR} used are from > meta-beagleboad, not from my bbappend. > > I tried to follow the instructions to add config fragments on the page > below but it did not worked too. > > http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#changing-the-configuration > > The strange thing is: My patch is applied but my defconfig, or config > fragment is not used. > I just want to add CONFIG_WATCHDOG_NOWAYOUT=y. > > I already did a cleasstate but no success. > > Any hints? > > > Regards, > > -- > *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