From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Building u-boot images in both kernel.bbclass:do_deploy() and linux.inc:do_compile_append()
Date: Sat, 29 Nov 2008 22:05:00 +0100 [thread overview]
Message-ID: <ggsaps$uch$1@ger.gmane.org> (raw)
In-Reply-To: <c384c5ea0811291149s5c02d3c8haad5995ce1ad1522@mail.gmail.com>
On 29-11-08 20:49, Leon Woestenberg wrote:
> Building u-boot images using mkimage is present in both
> kernel.bbclass:do_deploy() as well as in
> linux.inc:do_compile_append().
>
> Which one has preference in the long run, and why?
The one in do_deploy has more fancy features IIRC, but that should be
moved to do_compile, since we want to package the fancy one :)
The uImage that the kernel makefile generated should _not_ be used,
since in OE we generally know better which start & load address to use
and which compression method works best for us. Incidentally RMK agrees
with me on that for a change :)
regards,
Koen
next prev parent reply other threads:[~2008-11-29 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 19:49 Building u-boot images in both kernel.bbclass:do_deploy() and linux.inc:do_compile_append() Leon Woestenberg
2008-11-29 19:58 ` Tom Rini
2008-11-29 21:05 ` Koen Kooi [this message]
2008-11-29 21:10 ` Koen Kooi
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='ggsaps$uch$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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