Op 6 mrt. 2013, om 08:25 heeft Peter Kurrasch <gtin...@hotmail.com> het volgende geschreven:
> Hi Koen-- > > Thanks for the tip! I'm able to make changes to the kernel config and > generate "proper" objects that don't get wiped out the next time I try to > build something. I do have 2 questions, though.... >> 1) ./oebb.sh update >> 2) bitbake systemd-git >> 3) bitbake virtual/kernel -c menuconfig >> Did you save the resulting .config at this point? If not, you need to >> copy it back to the 'defconfig' in the metadata and increase >> (MACHINE_KERNEL_)PR in the recipe for the package managers to notice it. > First, I copied my changes to the file > meta-ti/recipes-kernel/linux/linux-mainline-3.2/beagleboard/defconfig like > you say and then modified the file meta-ti/conf/machine/include/omap3.inc to > change MACHINE_KERNEL_PR from "r122" to "r123". So my question is if it is > necessary and/or recommended that I bump up the _PR value with every change > to defconfig? Yes, but see below > It appears to me that I can make multiple changes to defconfig and the > change gets picked up right away when I go to build the kernel--without > changing the _PR to "r124", for example. But the packagemanager won't see the difference > > 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. regards, Koen _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
