From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/5] kernel.bbclass: move uImage handling to separate task
Date: Mon, 19 Dec 2011 17:02:00 +0400 [thread overview]
Message-ID: <4EEF35C8.3030607@gmail.com> (raw)
In-Reply-To: <D018C1C3-1814-4EB5-BB3D-87002117514E@dominion.thruhere.net>
On 12/19/2011 04:54 PM, Koen Kooi wrote:
>
> Op 19 dec. 2011, om 13:47 heeft Dmitry Eremin-Solenikov het volgende geschreven:
>
>>
>>
>> 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?
>
> No. If the machine.conf sets the UBOOT_* variables I should not need some magic unbreak-me variable to get kernel.bbclass to use them.
I see your point. I'll redo it so.
--
With best wishes
Dmitry
prev parent reply other threads:[~2011-12-19 13:10 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
[not found] ` <D018C1C3-1814-4EB5-BB3D-87002117514E@dominion.thruhere.net>
2011-12-19 13:02 ` Dmitry Eremin-Solenikov [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=4EEF35C8.3030607@gmail.com \
--to=dbaryshkov@gmail.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.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