From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Koen Kooi <public-koen-QLwJDigV5abLmq1fohREcCpxlwaOVQ5f@lo.gmane.org>
Subject: Re: [PATCH 1/5] kernel.bbclass: move uImage handling to separate task
Date: Mon, 19 Dec 2011 16:47:10 +0400 [thread overview]
Message-ID: <4EEF324E.8060203@gmail.com> (raw)
In-Reply-To: <5C0105D4-44BE-4584-9ED9-36970B91A34C@dominion.thruhere.net>
On 12/19/2011 12:13 AM, Koen Kooi wrote:
>
> Op 18 dec. 2011, om 20:47 heeft Dmitry Eremin-Solenikov het volgende geschreven:
>
>> As per org.oe.dev and meta-oe's kernel.bbclass move uImage creation to
>> separate task from do_deploy. This way the do_install task can also
>> benefit from generated uImage.
>>
>> The only major feature of oe-core's version (not to recreate uImage
>> if it exists) is retained in this patch.
>
> I still don't agree with that behaviour. The in-kernel uImage code is just like the in-kernel defconfigs: useless for people who aren't kernel developers.
Koen, that was addressed with KERNEL_RECREATE_UIMAGE variable.
Probably I should document it somewhere (in the commit message?
documentation.conf? smwh. else?). Would you agree with this patch + docs?
>
>> On the contra, as this version
>> was merged from meta-oe/org.oe.dev, new function has another feature:
>> it permits overriding the u-boot entrypoint via u-boot symbol.
>
> No it doesn't, since it doesn't recreate uImage.
It does.
BTW: I don't have much experience of uImage usage on ARM SoCs (I used
them only on Atmel boards, where things usually 'just worked' regarding
Kernel load address & Ko). On PowerPC I also didn't have too much
problems with upstream kernels (both from Linus'es tree and from
Freescale's one).
I understand your concern, that for your tasks, you have to recreate
uImage using your sane values. However for some people sane values are
ones present in upstream tree. Moreover, if you care about history, it
was specially changed in oe-core not to recreate uImage, as it caused
problems for some of the users.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2011-12-19 12:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 19:47 [PATCH 1/5] kernel.bbclass: move uImage handling to separate task Dmitry Eremin-Solenikov
2011-12-18 19:47 ` [PATCH 2/5] Move check that all installed files are shipped into insane.bbclass Dmitry Eremin-Solenikov
2011-12-18 23:29 ` Khem Raj
2011-12-19 0:02 ` Richard Purdie
2011-12-19 4:49 ` Khem Raj
2011-12-18 19:47 ` [PATCH 3/5] ncurses: drop compatibility symlink to remove QA warning Dmitry Eremin-Solenikov
2011-12-18 19:47 ` [PATCH 4/5] libatomics-ops: move docs to correct directory Dmitry Eremin-Solenikov
2011-12-19 12:18 ` Richard Purdie
2011-12-18 19:47 ` [PATCH 5/5] icecc.bbclass: also use icecc for kernel modules compilation Dmitry Eremin-Solenikov
2011-12-19 12:19 ` Richard Purdie
2011-12-18 20:13 ` [PATCH 1/5] kernel.bbclass: move uImage handling to separate task Koen Kooi
2011-12-18 20:27 ` Bruce Ashfield
2011-12-18 21:19 ` Koen Kooi
2011-12-19 1:39 ` Bruce Ashfield
2011-12-19 5:06 ` Khem Raj
2011-12-19 5:23 ` Bruce Ashfield
2011-12-19 9:03 ` Koen Kooi
2011-12-19 12:47 ` Dmitry Eremin-Solenikov [this message]
[not found] ` <D018C1C3-1814-4EB5-BB3D-87002117514E@dominion.thruhere.net>
2011-12-19 13:02 ` Dmitry Eremin-Solenikov
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=4EEF324E.8060203@gmail.com \
--to=dbaryshkov@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=public-koen-QLwJDigV5abLmq1fohREcCpxlwaOVQ5f@lo.gmane.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 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.