If I may add something here... I found that "bitbake -c rebuild" will unpack the kernel source from the tarball found in the cache, and rebuild it with a default config. This might (apart from the the fact the a rebuild takes more time than a recompile) be fine if there are no config modifications to carry forward between builds, but personally I have more and more modifications to the kernel config as I go along. If you're in the same shoes, try using:

bitbake -c patch linux-omap3 -f
bitbake -c menuconfig linux-omap3-2.6.31
bitbake -c compile linux-omap3-2.6.31 -f
bitbake -c deploy linux-omap3-2.6.31


On Wed, Jan 20, 2010 at 7:42 PM, ScottEllis <scottellis.developer@gmail.com> wrote:

When you settle on the patch you want, you can get it into the OE framework
this way.

cd ${OETMP}/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.32-r51

cp git/arch/arm/mach-omap2/board-overo.c

[edit git/arch/arm/mach-omap2/board-overo.c]

git diff git/arch/arm/mach-omap2/board-overo.c-orig
git/arch/arm/mach-omap2/board-overo.c > my-board.patch

cp my-board.patch


[edit org.openembedded.dev/recipes/linux/linux-omap3_2.6.32.bb]

 SRC_URI_append = " \
           file://${BOOT_SPLASH} \
+           file://my-board.patch;patch=1 \

Then rebuild and your patch will get applied by bitbake.

bitbake -c clean linux-omap3-2.6.32
bitbake -c rebuild linux-omap3-2.6.32

View this message in context: http://old.nabble.com/Where-to-make-kernel-changes--tp27230399p27246563.html
Sent from the Gumstix mailing list archive at Nabble.com.

Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
gumstix-users mailing list