how to compile my kernel(3.14) by adding wireless extendions support in menuconfig

[mutyalaraoneela]

Hi All,

platform : imx6sl

kernel    : 3.14    

I have downloaded the source code from the repository by following the steps in yocto build pdf, After downloading when I cross compiled my driver and copied onto the board, and insert it (insmod) it says unknown symbol in module "send_wireless_evnt", so now I want to add the "CONFIG_WIRELESS_EXT" support to my kernel.

Please tell me how to compile my kernel with the changes made in menuconfig.

When I bitbake again "bitbake core-imge-minimal", it is downloading the new kernel. but it is not building my kernel in which changes were made.

Please tell me how to do it????

Thanks in Advance.

[mutyalaraoneela]

Hi Gusarambula,

     I am doing this project for 3.14 kernel, for that I checked out 3.14 kernel source by following the document for yocto source is checked out in the path "/fsl-release-bsp/build/tmp/work/imx6sl-poky-linux-gnueabi/lkinux-imx/3.14.28-r0/git/"  there .config file is there. From the build folder when i issue the command "bitbake -c menuconfig linux-imx" it pops up a window for configuring the kernel and the changes which i made are getting reflected in .config file in the above mentioned path.

AND

in the "fsl-release-bsp/build/sources/meta-fsl-arm/recipes-kernel/"  I didn't find my kernel which was checked out in the above paragraph,  Instead of that 3.10, 2.6.35 kernel were checked out.

In the above mentioned link "building linux kernel" that shows the same kernel in the two different paths, In my case it is not the same.

I am curious to know which .config file it is taking for the compilation of my kernel???

Please help me to resolve this issue!!!!

Thanks in advance.

[gusarambula]

Mutyalarao Neelapala,

Since kernel is not intended to be a development environment but as means of distribution of customized linux images, it is not very good ad tracking changes.

It is possible that the changes you made won’t be reflected if you bake the kernel again as the already built packages will remain unchanged; this unless you make a clean state.

Please read the following community document for information on configuring and building the kernel both manually with the toolchain and within Yocto.

Building Linux Kernel