From: "Eric Bénard" <eric@eukrea.com>
To: Eric Nelson <eric.nelson@boundarydevices.com>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>,
Troy Kisky <troy.kisky@boundarydevices.com>
Subject: Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X
Date: Tue, 11 Dec 2012 09:23:17 +0100 [thread overview]
Message-ID: <20121211092317.0851432b@eb-e6520> (raw)
In-Reply-To: <50C6AF5E.4080302@boundarydevices.com>
Hi Eric,
Le Mon, 10 Dec 2012 20:58:22 -0700,
Eric Nelson <eric.nelson@boundarydevices.com> a écrit :
> | 6x_bootscript-nitrogen6x.txt: No such file or directory
Does that work if you do bibake u-boot-script-boundary before building
the image ?
Eric
next prev parent reply other threads:[~2012-12-11 8:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 16:06 [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X Otavio Salvador
2012-12-10 16:06 ` [meta-fsl-arm-extra][PATCH 1/3] u-boot-boundary: Add U-Boot recipe for Boundary Devices version Otavio Salvador
2012-12-10 16:06 ` [meta-fsl-arm-extra][PATCH 2/3] u-boot-script-boundary: Add recipe to deploy the boot scripts Otavio Salvador
2012-12-10 16:06 ` [meta-fsl-arm-extra][PATCH 3/3] nitrogen6x: Add machine definition Otavio Salvador
2012-12-10 16:11 ` [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X Otavio Salvador
2012-12-10 19:47 ` Eric Nelson
2012-12-10 19:50 ` Otavio Salvador
2012-12-11 3:58 ` Eric Nelson
2012-12-11 8:23 ` Eric Bénard [this message]
2012-12-11 14:09 ` Eric Nelson
2012-12-11 14:15 ` Otavio Salvador
2012-12-11 14:29 ` Eric Nelson
2012-12-11 14:35 ` Otavio Salvador
2012-12-11 13:27 ` Harmalkar, Subodh S.
2012-12-11 14:10 ` Otavio Salvador
2012-12-11 14:10 ` Otavio Salvador
2012-12-11 14:24 ` Eric Nelson
2012-12-11 14:35 ` Otavio Salvador
2012-12-11 15:48 ` Eric Nelson
2012-12-11 18:28 ` Otavio Salvador
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=20121211092317.0851432b@eb-e6520 \
--to=eric@eukrea.com \
--cc=eric.nelson@boundarydevices.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
--cc=troy.kisky@boundarydevices.com \
/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.