From: Marek Vasut <marex@denx.de>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Koen Kooi <koen@dominion.thruhere.net>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/7] Add basic fitImage support
Date: Tue, 28 Apr 2015 03:09:01 +0200 [thread overview]
Message-ID: <201504280309.01881.marex@denx.de> (raw)
In-Reply-To: <CAJTo0LaYpbN7VuyErJGj9e8mbY+uUZCGePgsMeMq=Eq+Op8aCQ@mail.gmail.com>
On Thursday, October 23, 2014 at 01:26:01 AM, Burton, Ross wrote:
> On 19 October 2014 20:15, Marek Vasut <marex@denx.de> wrote:
> > This series cleans up the code in kernel.bbclass and
> > separates out the uImage generation. The last patch
> > in this series then adds support for generation of the
> > advanced successor of the uImage, the fitImage.
> >
> > This series adds only very rudimentary support for
> > generation of fitImage. The advanced features might
> > be added in subsequent patches.
> >
> > I would also like to thank Richard for explaining to
> > me how to properly do the implementation and I hope
> > this series is at least close to that.
>
> For what it's worth I pulled these patches for initial testing and I got
>
> build failures with the fsl-ppc kernel:
> | "mkimage" command not found - U-Boot images will not be built
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc-lsb/buil
> ds/77/steps/BuildImages/logs/stdio
>
> These patches were not the only ones pulled into that branch, but they're
> the only relevant change that I can see. It looks like a native dependency
> disappeared somewhere, can you have a look at this?
Yikes, right. I found this and I'll repost the patches tomorrow. Sorry
this took so long.
Best regards,
Marek Vasut
prev parent reply other threads:[~2015-04-28 2:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 19:15 [PATCH 0/7] Add basic fitImage support Marek Vasut
2014-10-19 19:15 ` [PATCH 1/7] kernel: Clean up KERNEL_IMAGETYPE_FOR_MAKE Marek Vasut
2014-10-19 19:25 ` Otavio Salvador
2014-10-19 21:13 ` Marek Vasut
2014-10-19 21:26 ` Otavio Salvador
2014-10-22 20:39 ` Marek Vasut
2014-10-23 0:32 ` Otavio Salvador
2014-10-23 0:45 ` Marek Vasut
2014-10-19 19:15 ` [PATCH 2/7] kernel: Rework do_uboot_mkimage Marek Vasut
2014-10-19 19:15 ` [PATCH 3/7] kernel: Pull out the linux.bin generation Marek Vasut
2014-10-19 19:15 ` [PATCH 4/7] kernel: Pull uImage generation into separate class Marek Vasut
2014-10-19 21:29 ` Khem Raj
2014-10-19 22:31 ` Marek Vasut
2014-10-19 22:08 ` Bruce Ashfield
2014-10-19 22:29 ` Marek Vasut
2014-10-20 3:38 ` Bruce Ashfield
2014-10-20 10:26 ` Koen Kooi
2014-10-21 23:28 ` Marek Vasut
2014-10-22 8:42 ` Koen Kooi
2014-10-22 21:45 ` Marek Vasut
2014-10-26 11:29 ` Koen Kooi
2014-10-26 22:52 ` Marek Vasut
2014-10-27 6:59 ` Koen Kooi
2015-04-28 2:39 ` Marek Vasut
2015-04-28 8:22 ` Paul Eggleton
2014-10-22 20:51 ` Marek Vasut
2014-10-19 19:15 ` [PATCH 5/7] kernel: Separate out uboot_prep_kimage Marek Vasut
2014-10-19 19:15 ` [PATCH 6/7] kernel: Build DTBs early Marek Vasut
2014-10-19 19:15 ` [PATCH 7/7] kernel: Add basic fitImage support Marek Vasut
2014-10-19 19:32 ` [PATCH 0/7] " Otavio Salvador
2015-04-28 1:32 ` Marek Vasut
2014-10-22 23:26 ` Burton, Ross
2014-10-23 0:01 ` Marek Vasut
2015-04-28 1:09 ` Marek Vasut [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=201504280309.01881.marex@denx.de \
--to=marex@denx.de \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=ross.burton@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