Re: [Balloon] Kernel hacking workflow
|This message is part of the following thread:|
|the complete thread tree sorted by date|
|Peter Clifton at|
|Nick Bane at|
>> My workflow goes something like this: >> - build kernel (make at menuconfig2 top level) >> - download to board, test, discover bugs as expected >> - in build tree: >> - quilt pop balloon3-i2s
>> - edit various files. Some of these are in the patch, others won't >> be. For example, I've put debug code in /arch/arm/mach-pxa/mfp-pxa2xx.c >> which I don't expect to become part of the patch but makes my >> development job easier.
>> - quilt refresh >> - back at menuconfig2 top level, make again.