[meta-ti] Turning off kernel config option

[Richard Purdie]

On Tue, 2012-08-07 at 11:38 -0400, Denys Dmytriyenko wrote:
> On Tue, Aug 07, 2012 at 05:32:36PM +0200, Koen Kooi wrote:
> > 
> > Op 7 aug. 2012, om 17:30 heeft Denys Dmytriyenko <denys at ti.com> het volgende geschreven:
> > 
> > > On Tue, Aug 07, 2012 at 10:02:24AM +0100, Jack Mitchell wrote:
> > >> I am trying to turn of CONFIG_SPI_DEBUG in the beaglebone BSP from
> > >> meta-ti. I am using the poky distro configuration and I have changed
> > >> the defconfig in
> > >> meta-ti/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig
> > >> but it still builds with CONFIG_SPI_DEBUG enabled.
> > > 
> > > That should be the correct location, please make sure you re-do the unpack 
> > > task - if you previously built the kernel with the old defconfig, it will be 
> > > stored in the work directory and won't be copied from the repository above, 
> > > until you repeat the do_unpack task, i.e. by clenaing the build.
> 
> BTW, no need to clean the entire build, just the kernel build:
> 
> $ bitbake virtual/kernel -c clean
> 
> > Or just increment PR as you're supposed to, it's an output change after all. 
> > No need to check anything if you do it properly :) 
> 
> Well, but then you are staring to change the recipe, which might be overkill 
> for a simple defconfig change you want to test. If you go that route, you may 
> want to create your own custom layer with the modified defconfig overlayed on 
> top of meta-ti and a simple .bbappend with PRINC. That way your changes will 
> be detached from meta-ti and you won't need to merge the recipe changes every 
> time meta-ti updates... Although, there's no way to bbappend the defconfig 
> itself - that's where config fragments come to play.

With the recent changes to OE-Core, you can edit the defconfig, the
system will notice the checksum change and automatically rerun the
unpack and subsequent steps automagically.

If the PR server is enabled, it will bump PR for you too.

Cheers,

Richard