Yocto Layers - config files being ignored?

[ZSher1]

Hello again,

Been posting a lot on this but I haven't wanted to put too many questions in one post. I've been building Yocto iot-devkit images using this post from intel:

https://software.intel.com/en-us/blogs/2015/03/04/creating-a-yocto-image-for-the-intel-galileo-board... https://software.intel.com/en-us/blogs/2015/03/04/creating-a-yocto-image-for-the-intel-galileo-board...

However, I've been trying to add new kernel config files to them, and I guess I'm confused about what does and does not get looked at when bitbake builds all the recipes.

Inside the meta-intel-iot-devkit layer, there are a TON of config files, that should add wireless network support for everything, including Atheros drivers. They have all the kernel config choices I want. However, although the config files are added in a .bbappend file, these different config files seem to do a whole lot of nothing.

Am I totally missing another file, or am I right in thinking these different kernel configs are just being totally ignored.

For reference, if you follow that tutorial and are in the iotdk folder, here's where each of the files I'm talking about are:

bbappend file that references the wireless config files:

meta-intel-iot-devkit/recipes-kernel/linux/linux-yocto-quark_3.8.bbappend

.cfg file for atheros

meta-intel-iot-devkit/recipes-kernel/linux/linux-yocto-quark/iot-devkit/wlan-atheros.cfg

[Carlos_M_Intel]

Hi zsherin,

Just to be sure, what you want is to include drivers in the image, like the drivers for Atheros, Is this right?

If this is the case you need to enable these modules with the menuconfig or in the defconfig file.

There are some things that are enabled and other that are not this is the reason of why there are some files that include it in the bitbake of the image and others that are not.

Kind Regards,

Charlie

[ZSher1]

Hi CMata_Intel,

Thanks for the quick response. How do you use menuconfig for the new images? Whenever I use "bitbake -c menuconfig iot-devkit-prof-dev-image" it says

Task do_menuconfig does not exist for target iot-devkit-prof-dev-image. Close matches: do_configure

Am I missing a new thing in the bitbake docs?

Thanks,

Zach

[Carlos_M_Intel]

Hi Zach,

Do you have updates in this?

Have you tried with bitbake virtual/kernel -c menuconfig ?

Regards,

Charlie

[Carlos_M_Intel]

Hi Zach,

Did you try with bitbake virtual/kernel -c menuconfig?

Regards,

Charlie

[Matthias_H_Intel]

the menuconfig would only generate a .config to /tmp/work/.../.config. However, in order to have your kernel recipe picking up you'd have to modify the "defconfig" file in your recipe files (or better generate a patch which is included in a "*bb_append" file. See e.g. my blog https://software.intel.com/en-us/blogs/2015/02/27/intel-edison-adding-kernel-modules-to-yocto-exampl... IoT - Intel® Edison - adding kernel modules to Yocto* - example "batman" | Intel® Developer Zone