From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH oe-core v5] linux-dtb: add multi-dtb build support and keep dtb in deploy cache package
Date: Fri, 06 Jan 2012 11:01:24 +0000 [thread overview]
Message-ID: <1325847684.20759.83.camel@ted> (raw)
In-Reply-To: <1325836261-4251-1-git-send-email-b19537@freescale.com>
On Fri, 2012-01-06 at 15:51 +0800, b19537@freescale.com wrote:
> From: Zhenhua Luo <b19537@freescale.com>
>
> DEPLOY_DIR_IMAGE is the images deploy folder - tmp/deploy/images
> DEPLOYDIR is the deploy folder of linux - deploy-linux-qoriq-sdk
>
> Signed-off-by: Zhenhua Luo <b19537@freescale.com>
> ---
> meta/recipes-kernel/linux/linux-dtb.inc | 30 +++++++++++++++++++++---------
> 1 files changed, 21 insertions(+), 9 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-dtb.inc b/meta/recipes-kernel/linux/linux-dtb.inc
> index 7ec7584..f1bd2bf 100644
> --- a/meta/recipes-kernel/linux/linux-dtb.inc
> +++ b/meta/recipes-kernel/linux/linux-dtb.inc
> @@ -13,15 +13,27 @@ python __anonymous () {
> d.setVar("PACKAGES", "%s kernel-devicetree" % packages)
> }
>
> -do_install_append() {
> +kernel_do_deploy_append() {
> if test -n "${KERNEL_DEVICETREE}"; then
> - dtc -I dts -O dtb ${KERNEL_DEVICETREE_FLAGS} -o devicetree ${KERNEL_DEVICETREE}
> - install -m 0644 devicetree ${D}/boot/devicetree-${KERNEL_VERSION}
> - install -d ${DEPLOY_DIR_IMAGE}
> - install -m 0644 devicetree ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGE_BASE_NAME}.dtb
> - cd ${DEPLOY_DIR_IMAGE}
> - rm -f ${KERNEL_IMAGE_SYMLINK_NAME}.dtb
> - ln -sf ${KERNEL_IMAGE_BASE_NAME}.dtb ${KERNEL_IMAGE_SYMLINK_NAME}.dtb
> + for DTS_FILE in ${KERNEL_DEVICETREE}; do
> + DTS_BASE_NAME=`basename ${DTS_FILE} | awk -F "." '{print $1}'`
> + DTB_NAME=`echo ${KERNEL_IMAGE_BASE_NAME} | sed "s/${MACHINE}/${DTS_BASE_NAME}/g"`
> + DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed "s/${MACHINE}/${DTS_BASE_NAME}/g"`
> + dtc -I dts -O dtb ${KERNEL_DEVICETREE_FLAGS} -o devicetree ${DTS_FILE}
> + install -m 0644 devicetree ${D}/boot/devicetree-${DTS_BASE_NAME}-${KERNEL_VERSION}
> + install -d ${DEPLOY_DIR_IMAGE}
> + install -m 0644 devicetree ${DEPLOY_DIR_IMAGE}/${DTB_NAME}.dtb
> + rm -f devicetree
> + cd ${DEPLOY_DIR_IMAGE}
> + rm -f ${DTB_SYMLINK_NAME}.dtb
> + ln -sf ${DTB_NAME}.dtb ${DTB_SYMLINK_NAME}.dtb
> + cd -
> +
> + install -d ${DEPLOYDIR}
> + install -m 0644 ${DEPLOY_DIR_IMAGE}/${DTB_NAME}.dtb ${DEPLOYDIR}/${DTB_NAME}.dtb
> + cd ${DEPLOYDIR}
> + ln -sf ${DTB_NAME}.dtb ${DTB_SYMLINK_NAME}.dtb
> + cd -
> + done
>
This is close but its still not 100% right. If you put the files into
${DEPLOYDIR} (such as ${DEPLOYDIR}/${DTB_NAME}.dtb), the sstate code
itself will ensure it makes it to ${DEPLOY_DIR_IMAGE}/${DTB_NAME}.dtb.
You can therefore remove the last bit of duplication in this function,
don't touch ${DEPLOY_DIR_IMAGE} at all and the files will still appear
there, just like kernel_do_deploy() itself does.
Cheers,
Richard
prev parent reply other threads:[~2012-01-06 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 7:51 [PATCH oe-core v5] linux-dtb: add multi-dtb build support and keep dtb in deploy cache package b19537
2012-01-06 11:01 ` Richard Purdie [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=1325847684.20759.83.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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