Hi! What configuration kernel build really uses - .config or defconfig? It seems, that menuconfig (bitbake -c menuconfig ) use always .config file.
I have problem that changes in defconfig are not seen in kernel features. Instead they seem the same that are in .config file I have tried configuration fragments, patches and providing defconfig directly. They all seem to give proper defconfig. However, menuconfig never provide the changed configurations. Also, for instance when I try to configure HW EEC operation for NAND flash using CONFIG_MTD_NAND_OMAP_BCH. omap2.c reports that "CONFIG_MTD_NAND_OMAP_BCH is not enabled". I've been workin on beaglebone variant - layer over beaglebone. Build Configuration: BB_VERSION = "1.17.0" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "beaglebone" DISTRO = "angstrom" DISTRO_VERSION = "v2012.12" TUNE_FEATURES = "armv7a vfp neon cortexa8" TARGET_FPU = "vfp-neon" oe_sitecno oe_emergence = "<unknown>:<unknown>" meta-angstrom = "angstrom-v2012.12-yocto1.3:b7f8207b94d9a0ece73ad212a193cb2c95bd17ee" These setting give kernel 3.8.11. Is there something I have missed? Thanks in advance, Matti _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
