From: Siddharth Heroor <heroor@ti.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>,
"Rini, Tom" <trini@ti.com>
Subject: Re: [PATCHv2 4/4] ti43x, omap-a15: switch KERNEL_IMAGETYPE to zImage by default
Date: Thu, 26 Sep 2013 21:20:01 +0530 [thread overview]
Message-ID: <524457A9.8060908@ti.com> (raw)
In-Reply-To: <20130926153525.GR14528@edge>
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 <chase.maupin@ti.com>
>>
>> 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
prev parent reply other threads:[~2013-09-26 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 19:49 [PATCHv2 4/4] ti43x, omap-a15: switch KERNEL_IMAGETYPE to zImage by default Denys Dmytriyenko
2013-09-26 11:59 ` Maupin, Chase
2013-09-26 15:04 ` Siddharth Heroor
2013-09-26 15:35 ` Denys Dmytriyenko
2013-09-26 15:50 ` Siddharth Heroor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=524457A9.8060908@ti.com \
--to=heroor@ti.com \
--cc=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=trini@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.