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.
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?
Do you have updates in this?
Have you tried with bitbake virtual/kernel -c menuconfig ?
Did you try with bitbake virtual/kernel -c menuconfig?
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 IoT - Intel® Edison - adding kernel modules to Yocto* - example "batman" | Intel® Developer Zone