From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
jimwall@q.com, brian@crystalfontz.com
Subject: Re: [meta-fsl-arm][PATCH 1/2] barebox: Rework do_configure_prepend to do_pre_configure
Date: Wed, 07 Aug 2013 16:46:49 +0200 [thread overview]
Message-ID: <52025DD9.7030206@free-electrons.com> (raw)
In-Reply-To: <CAP9ODKo72428GkVMxWCzyB9TqeKp=xjYpnwRDKu_bSwg95JLEA@mail.gmail.com>
Hello,
On 07/08/2013 15:35, Otavio Salvador wrote:
> Hello Alexandre,
>
> On Wed, Aug 7, 2013 at 7:40 AM, Alexandre Belloni
> <alexandre.belloni@free-electrons.com> wrote:
>> Defining a new task instead of using configure_prepend allows inheriting
>> recipes to override the pre_configure task.
>>
>> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> I applied both batches to master branch. Thanks for those.
>
> I'd like to know if you'd be willing to prepare a patchset to move
> barebox to OE-Core as it should be put there, not in meta-fsl-arm?
>
The actual current goal is to get support for the i.mx28 based cfa-100xx
boards in meta-fsl-arm-extra. As the boards are supported by the
mainline barebox and they have a defconfig there, I had to get the
flexibility to do:
do_pre_configure() {
oe_runmake cfa10036_defconfig
}
in my recipe.
Also, barebox_default_env is now generated in common/ and I want to had
support for custom default environment.
What features do you think would be missing before submitting that to
oe-core ?
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-08-07 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 10:40 [meta-fsl-arm][PATCH 1/2] barebox: Rework do_configure_prepend to do_pre_configure Alexandre Belloni
2013-08-07 10:40 ` [meta-fsl-arm][PATCH 2/2] barebox: move environment deployment to its own task Alexandre Belloni
2013-08-07 13:35 ` [meta-fsl-arm][PATCH 1/2] barebox: Rework do_configure_prepend to do_pre_configure Otavio Salvador
2013-08-07 14:46 ` Alexandre Belloni [this message]
2013-08-07 14:58 ` Eric Bénard
2013-08-07 16:02 ` Otavio Salvador
-- strict thread matches above, loose matches on Subject: below --
2013-08-07 10:27 Alexandre Belloni
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=52025DD9.7030206@free-electrons.com \
--to=alexandre.belloni@free-electrons.com \
--cc=brian@crystalfontz.com \
--cc=jimwall@q.com \
--cc=maxime.ripard@free-electrons.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.