Hi Koen--
Thanks for the explanations. One more question:
On 3/6/2013 3:19 AM, Koen Kooi wrote:
My second question is if it's okay and/or a good idea to change the _PR_append
value instead? In looking at the
meta-ti/recipes-kernel/linux/linux-mainline_3.2.bb I saw the line:
MACHINE_KERNEL_PR_append = "a"
...and I was wondering if changing that to "b" would have the same effect as changing
"r122" to "r123"? The location of the .bb file makes it easier to find than hunting down
the omap3.inc file, so if it works just as well I'd rather change the _PR_append instead.
Exactly! The PR_append is for changes to the kernel that don't influence
external modules (sgx, dsp etc) and the MACHINE_KERNEL_PR is increased when
external modules do need to get rebuilt.
When I'm in the process of making a kernel change, re-compiling,
watching it fail, make another change, etc. it can be a bit of a hassle
to bump up either MACHINE_KERNEL_PR or the _PR_append value. Instead,
I've tried just touching the file
.../linux-mainline-3.2/beagleboard/defconfig each time I make a change
and then re-build. It "seems to work" but I'm not totally convinced
that everything is in fact okay. Would you consider this an okay way to
go or is there something I've overlooked (or don't know!)?
Thanks.
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel