From: Denys Dmytriyenko <denis@denix.org>
To: Yannick Gicquel <yannick.gicquel@iot.bzh>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH v2 2/4] u-boot: deploy u-boot-nodtb and dtb files
Date: Wed, 20 Apr 2016 15:51:20 -0400 [thread overview]
Message-ID: <20160420195120.GQ16135@denix.org> (raw)
In-Reply-To: <1461160239-7799-3-git-send-email-yannick.gicquel@iot.bzh>
On Wed, Apr 20, 2016 at 03:50:37PM +0200, Yannick Gicquel wrote:
> This enable the deployment of u-boot-nodtb.bin and u-boot.dtb files.
>
> Signed-off-by: Yannick Gicquel <yannick.gicquel@iot.bzh>
> ---
> meta/classes/uboot-sign.bbclass | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/meta/classes/uboot-sign.bbclass b/meta/classes/uboot-sign.bbclass
> index 63a5181..adb24d4 100644
> --- a/meta/classes/uboot-sign.bbclass
> +++ b/meta/classes/uboot-sign.bbclass
> @@ -38,6 +38,22 @@ UBOOT_NODTB_SYMLINK ?= "u-boot-nodtb-${MACHINE}.${UBOOT_SUFFIX}"
> # Following is relevant only for u-boot recipes:
> #
>
> +do_deploy_append_pn-u-boot () {
Same question here about _pn-u-boot.
> + # OF_SEPARATE generated files deployment
> + if [ -f ${B}/${UBOOT_DTB_BINARY} ]; then
> + install ${B}/${UBOOT_DTB_BINARY} ${DEPLOYDIR}/${UBOOT_DTB_IMAGE}
> + rm -f ${UBOOT_DTB_BINARY} ${UBOOT_DTB_SYMLINK}
> + ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_SYMLINK}
> + ln -sf ${UBOOT_DTB_IMAGE} ${UBOOT_DTB_BINARY}
> + fi
> + if [ -f ${B}/${UBOOT_NODTB_BINARY} ]; then
> + install ${B}/${UBOOT_NODTB_BINARY} ${DEPLOYDIR}/${UBOOT_NODTB_IMAGE}
> + rm -f ${UBOOT_NODTB_BINARY} ${UBOOT_NODTB_SYMLINK}
> + ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_SYMLINK}
> + ln -sf ${UBOOT_NODTB_IMAGE} ${UBOOT_NODTB_BINARY}
> + fi
> +}
> +
> do_install_prepend_pn-u-boot () {
> # Concatenate U-Boot w/o DTB & DTB with public key
> # (cf. kernel-fitimage.bbclass for more details)
> --
> 1.9.1
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2016-04-20 20:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 13:50 [RFC][PATCH v2 0/4] U-Boot verified boot basic support Yannick Gicquel
2016-04-20 13:50 ` [RFC][PATCH v2 1/4] u-boot: basic support of dtb append for verified boot Yannick Gicquel
2016-04-20 15:23 ` Tom Rini
2016-04-20 19:33 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 19:49 ` [RFC][PATCH v2 " Denys Dmytriyenko
2016-04-20 21:03 ` Tom Rini
2016-04-21 10:25 ` Yannick GICQUEL
2016-04-21 14:06 ` Andreas Oberritter
2016-04-21 19:55 ` Yannick GICQUEL
2016-04-24 12:56 ` Bernhard Reutner-Fischer
2016-04-20 13:50 ` [RFC][PATCH v2 2/4] u-boot: deploy u-boot-nodtb and dtb files Yannick Gicquel
2016-04-20 15:23 ` Tom Rini
2016-04-20 19:34 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 19:51 ` Denys Dmytriyenko [this message]
2016-04-20 13:50 ` [RFC][PATCH v2 3/4] kernel: fitimage: support device tree compiler options Yannick Gicquel
2016-04-20 15:23 ` Tom Rini
2016-04-20 19:34 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 13:50 ` [RFC][PATCH v2 4/4] kernel: fitimage: basic support for fitimage signature Yannick Gicquel
2016-04-20 15:23 ` Tom Rini
2016-04-20 19:35 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 15:23 ` [RFC][PATCH v2 0/4] U-Boot verified boot basic support Tom Rini
2016-04-20 19:43 ` Denys Dmytriyenko
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=20160420195120.GQ16135@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=yannick.gicquel@iot.bzh \
/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