On 9/26/2013 9:05 PM, Denys Dmytriyenko wrote: > On Thu, Sep 26, 2013 at 08:34:27PM +0530, Siddharth Heroor wrote: >> On 9/26/2013 5:29 PM, Maupin, Chase wrote: >>> Acked-by: Chase Maupin <[email protected]> >> >> Just a question - is it possible to override the KERNEL_IMAGETYPE in a >> branding.inc file? In general, we want to move to zImage for GLSDK but >> some customers who might want to stay on uImage as they ramp. > > It won't be very easy to do from a branding file. That's why I had to rev > the other patch to keep GLSDK 3.8 and AMSDK 3.2 kernel recipes on uImage, but > switch other platforms to zImage which already have recent enough u-boot... > > When you have a new kernel/u-boot that prefers zImage (like the new > linux-ti-staging_git.bb we have for 3.12 integration), you can set the image > type to zImage in the kernel recipe, or rather not specify it at all, since > it will be picked up from machine config. > > In other words, after the setting in the machine config, you have one more > option to override it in a specific kernel recipe. That way if your branding > selects latest kernel/u-boot combo, you get zImage by default from the > machine > config. But if branding selects 3.2 kernel with early u-boot, it gets > overwritten back to uImage... >
Got it. Thanks, Sid _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
