Workflow for Custom Kernel + Config

Hi Guys,

I am wondering if anyone can recommend a good workflow for maintaining a custom kernel (or at this stage, the stock kernel with a custom config) using openembedded. Is this something that a local overlay is suitable for?

In that case, looking at the dependencies for the beagleboard machine, my local overlay would contain the /linux/linux-omap2_git.bb in the correct place, and updated defconfig.

Does anyone have any other experience with this? I would like to do this the ‘proper’ way, instead of just modifying the defconfig in the OE checkout

Thanks,

John