From: Marek Vasut <marex@denx.de>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 8/8] kernel: Build uImage only when really needed
Date: Tue, 28 Apr 2015 23:15:19 +0200 [thread overview]
Message-ID: <201504282315.19422.marex@denx.de> (raw)
In-Reply-To: <553FD4E4.3000900@windriver.com>
On Tuesday, April 28, 2015 at 08:43:48 PM, Bruce Ashfield wrote:
> On 2015-04-28 12:38 PM, Marek Vasut wrote:
> > Build the uImage file using the kernel build system only when
> > it is really required, which is only in case KEEPUIMAGE == yes.
> > Otherwise, just build zImage, since the Yocto build system will
> > handle the uImage generation for us.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
> > Cc: Koen Kooi <koen@dominion.thruhere.net>
> > Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
> > Cc: Ross Burton <ross.burton@intel.com>
> > Cc: Bruce Ashfield <bruce.ashfield@windriver.com>
> > ---
> >
> > meta/classes/kernel-uimage.bbclass | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/meta/classes/kernel-uimage.bbclass
> > b/meta/classes/kernel-uimage.bbclass index ce8f96f..acde9ae 100644
> > --- a/meta/classes/kernel-uimage.bbclass
> > +++ b/meta/classes/kernel-uimage.bbclass
> > @@ -6,6 +6,14 @@ python __anonymous () {
> >
> > depends = d.getVar("DEPENDS", True)
> > depends = "%s u-boot-mkimage-native" % depends
> > d.setVar("DEPENDS", depends)
> >
> > +
> > + # Override KERNEL_IMAGETYPE_FOR_MAKE variable, which is internal
> > + # to kernel.bbclass . We override the variable here, since we need
> > + # to build uImage using the kernel build system if and only if
> > + # KEEPUIMAGE != yes. Otherwise, we pack compressed vmlinux into
> > + # the uImage .
>
> I keep reading this, and must be inverting the logic in my head.
>
> If we've set KEEPUIMAGE = yes, that means we just want to let the
> kernel build the uImage and perform no extra generation steps.
>
> When I read this, it looks like if I set the keep flag, I'll be
> overriden to build a zImage. Is that intentional ? I'd think we
> would have just left it alone or set it to uImage (unless we
> are saying that everyone should be building zImage now .. but
> I know some old ppc targets that do want to build uImages).
Uhhh, you're obviously right. The logic in the __anonymous function is
clearly inverted. Thanks for spotting this!
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-04-28 21:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 16:38 [PATCH 0/8] Add basic fitImage support Marek Vasut
2015-04-28 16:38 ` [PATCH 1/8] kernel: Clean up KERNEL_IMAGETYPE_FOR_MAKE Marek Vasut
2015-04-28 16:38 ` [PATCH 2/8] kernel: Rework do_uboot_mkimage Marek Vasut
2015-04-28 16:38 ` [PATCH 3/8] kernel: Pull out the linux.bin generation Marek Vasut
2015-04-28 16:38 ` [PATCH 4/8] kernel: Pull uImage generation into separate class Marek Vasut
2015-04-28 18:44 ` Bruce Ashfield
2015-04-28 21:16 ` Marek Vasut
2015-05-04 21:41 ` Marek Vasut
2015-05-12 14:15 ` Paul Eggleton
2015-05-12 15:38 ` Bruce Ashfield
2015-05-12 16:18 ` Paul Eggleton
2015-05-12 19:27 ` Marek Vasut
2015-05-12 20:57 ` Paul Eggleton
2015-05-12 22:18 ` Marek Vasut
2015-05-12 22:27 ` Paul Eggleton
2015-05-13 7:17 ` Marek Vasut
2015-04-28 16:38 ` [PATCH 5/8] kernel: Separate out uboot_prep_kimage Marek Vasut
2015-04-28 16:38 ` [PATCH 6/8] kernel: Build DTBs early Marek Vasut
2015-04-28 16:38 ` [PATCH 7/8] kernel: Add basic fitImage support Marek Vasut
2015-04-28 16:38 ` [PATCH 8/8] kernel: Build uImage only when really needed Marek Vasut
2015-04-28 18:43 ` Bruce Ashfield
2015-04-28 21:15 ` Marek Vasut [this message]
2015-04-28 18:45 ` [PATCH 0/8] Add basic fitImage support Bruce Ashfield
2015-04-28 20:06 ` Marek Vasut
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=201504282315.19422.marex@denx.de \
--to=marex@denx.de \
--cc=bruce.ashfield@windriver.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox