From: "Eric Bénard" <eric@eukrea.com>
To: David Vincent <freesilicon@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] barebox: Add recipe
Date: Mon, 28 Jul 2014 16:42:00 +0200 [thread overview]
Message-ID: <20140728164200.55019693@e6520eb> (raw)
In-Reply-To: <CAKRNOGx_e_cNLuzhETFuL2k12fhGsHBPdYT9ND8uP_F67=VA7A@mail.gmail.com>
Hi David,
Le Mon, 28 Jul 2014 14:15:12 +0200,
David Vincent <freesilicon@gmail.com> a écrit :
> > Why don't you use $BAREBOX_BINARY instead of hardcoding
> > barebox-flash-image which won't work on old versions of barebox where
> > barebox's binary is named barebox.bin ?
>
> I didn't know that, but I am not sure I can use $BAREBOX_BINARY since
> this variable is used in $DEPLOY_DIR. I tried to mimic u-boot recipe
> behavior as much as possible.
>
you can use the variable as it's defined upper. u-boot recipe does it
this way :
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-bsp/u-boot/u-boot.inc#n19
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-bsp/u-boot/u-boot.inc#n63
FWIW you can find here the initial barebox recipe we have in
meta-fsl-arm :
https://github.com/Freescale/meta-fsl-arm/tree/master/recipes-bsp/barebox
Best regards,
Eric
next prev parent reply other threads:[~2014-07-28 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 9:55 [PATCH] barebox: Add recipe David Vincent
2014-07-28 10:23 ` Richard Purdie
[not found] ` <CAKRNOGwGr3BM8FTMoqjNQ+p0tFKUj55RdyL+0wemf_7f1r1UcQ@mail.gmail.com>
2014-07-28 12:02 ` David Vincent
2014-07-30 11:46 ` Stefan Müller-Klieser
2014-07-30 16:56 ` Khem Raj
2014-07-28 11:58 ` Eric Bénard
2014-07-28 12:15 ` David Vincent
2014-07-28 14:42 ` Eric Bénard [this message]
2014-07-30 9:40 ` David Vincent
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=20140728164200.55019693@e6520eb \
--to=eric@eukrea.com \
--cc=freesilicon@gmail.com \
--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