I want to experiment with some kernel patches for beagle (twl4030
sound). Is there a good howto on this?
Can openembedded help construct the kernel development environment?
I want to experiment with some kernel patches for beagle (twl4030
sound). Is there a good howto on this?
Can openembedded help construct the kernel development environment?
I want to experiment with some kernel patches for beagle (twl4030
sound). Is there a good howto on this?
Basically: add your patches to the recipe, build, test, repeat.
regards,
Koen
But in terms of developing the patches? Should that be done within the
openembedded area or in a completely separate code tree?
Is there a simple way to use openembedded to construct the code tree
from its recipe to use that as the basis for patch development?
I want to experiment with some kernel patches for beagle (twl4030
sound). Is there a good howto on this?Basically: add your patches to the recipe, build, test, repeat.
But in terms of developing the patches? Should that be done within the
openembedded area or in a completely separate code tree?
Most of the time I develop in the oe work dir.
Is there a simple way to use openembedded to construct the code tree
from its recipe to use that as the basis for patch development?
bitbake virtual/kernel -cpatch
This will apply all patches but not compile.
You might want to familiarize yourself with quilt if you are not already
(or make a copy of the source dir so you can diff later).
Have fun!
Frans
What I do, is use this script
To get a simple cross compiling environment using the toolchain
created by openembedded, and then I can use git for my normal
workflow.
The patches generated by git format-patch can be used in your oe recipes.
vmjl
Thanks for that.