[meta-freescale] adding kernel configuration fragments to wandboard kernel

[Mike Wilson]

Thanks Bruce and Otavio. I understand better now.
I took the .config and copied it to my linux/files directory/defconfig.
I have verified that changes there make it into .config.
Now I can keep the config changes I need to make under my local version control, this should work fine for my needs.

Thanks!

-----Original Message-----
From: otavio.salvador at gmail.com [mailto:otavio.salvador at gmail.com] On Behalf Of Otavio Salvador
Sent: Wednesday, February 12, 2014 5:42 AM
To: Mike Wilson
Cc: meta-freescale at yoctoproject.org
Subject: Re: [meta-freescale] adding kernel configuration fragments to wandboard kernel

On Tue, Feb 11, 2014 at 6:09 PM, Mike Wilson <mwilson at kymetacorp.com> wrote:
> Q: what is the right way to modify the kernel config when using 
> linux-wandboard recipes?
>
>
>
> The yocto manuals say that you can define fragment files in your own 
> layer, which I have done.
>
> recipes-kernel/linux/linux-wandboard_3.0.35.bbappend is being read by 
> the build system, and the .cfg files are being picked up, because they 
> get copied to the kernel build directory:
>
> .../build/tmp/work/wandboard_dual-poky-linux-gnueabi/linux-wandboard/3
> .0.35-r0/i2c-spidev.cfg
>
> defconfig is in the same directory.
>
> The contents of i2c-spidev.cfg never make it into the git/.config 
> file. I noticed that the code to do this is in kernel-yocto.bbclass, 
> but this isn't included by any of the imx or wandboard kernel recipes. 
> In fact, I attempted to include it, but I ended up with the yocto 
> kernel source, hmm, not so good.
>
>
>
> What is your suggestion? Forget the fragment idea?

meta-fsl-arm and meta-fsl-arm-extra kernels does not use the Linux Yocto framework so you must to apply patches or provide replacement defconfig files to adapt the kernel.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750