From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] linux-dtb.inc: Fix dtb generation for kernels newer than 3.8
Date: Sat, 17 Aug 2013 21:20:27 -0400 [thread overview]
Message-ID: <5210215B.5060908@windriver.com> (raw)
In-Reply-To: <1376678068-31668-1-git-send-email-otavio@ossystems.com.br>
On 13-08-16 2:34 PM, Otavio Salvador wrote:
> The 3.8 kernel has change the default directory where the dtb file is
> stored. The change has been done at:
Indeed. I've been working around this with the reference boards during
my efforts to bump them to 3.10. I just didn't have my patch quite
ready yet .. so let's review this one!
>
> ,----[ Quote of 3.8 kernel change ]
> | commit 499cd8298628eeabf0eb5eb6525d4faa0eec80d8
> | Author: Grant Likely <grant.likely@secretlab.ca>
> | Date: Tue Nov 27 16:29:11 2012 -0700
> |
> | ARM: dt: change .dtb build rules to build in dts directory
> |
> | The current rules have the .dtb files build in a different directory
> | from the .dts files. The only reason for this is that it was what
> | PowerPC has done historically. This patch changes ARM to use the generic
> | dtb rule which builds .dtb files in the same directory as the source .dts.
> |
> | Cc: Russell King <linux@arm.linux.org.uk>
> | Cc: Arnd Bergmann <arnd@arndb.de>
> | Acked-by: Olof Johansson <olof@lixom.net>
> | Cc: linux-arm-kernel@lists.infradead.org
> | Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> | [swarren: added rm command for old stale .dtb files]
> | Signed-off-by: Stephen Warren <swarren@nvidia.com>
> | Signed-off-by: Rob Herring <rob.herring@calxeda.com>
> `----
>
> This change adds support for both places to backward and forward
> compatibility.
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> meta/recipes-kernel/linux/linux-dtb.inc | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-dtb.inc b/meta/recipes-kernel/linux/linux-dtb.inc
> index cebc76a..6b8f1a5 100644
> --- a/meta/recipes-kernel/linux/linux-dtb.inc
> +++ b/meta/recipes-kernel/linux/linux-dtb.inc
> @@ -15,8 +15,12 @@ do_install_append() {
> DTB_BASE_NAME=`basename ${DTB} .dtb`
> DTB_NAME=`echo ${KERNEL_IMAGE_BASE_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> + DTB_PATH="${B}/arch/${ARCH}/boot/dts/${DTB}"
> oe_runmake ${DTB}
> - install -m 0644 ${B}/arch/${ARCH}/boot/${DTB} ${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.dtb
> + if [ ! -e "${DTB_PATH}" ]; then
> + DTB_PATH="${B}/arch/${ARCH}/boot/${DTB}"
> + fi
perfect. Just what I was looking for, allowing the older style
kernels to continue to work.
> + install -m 0644 ${DTB_PATH} ${D}/${KERNEL_IMAGEDEST}/devicetree-${DTB_SYMLINK_NAME}.dtb
> done
> fi
> }
> @@ -31,8 +35,12 @@ do_deploy_append() {
> DTB_BASE_NAME=`basename ${DTB} .dtb`
> DTB_NAME=`echo ${KERNEL_IMAGE_BASE_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> DTB_SYMLINK_NAME=`echo ${KERNEL_IMAGE_SYMLINK_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g"`
> + DTB_PATH="${B}/arch/${ARCH}/boot/dts/${DTB}"
> + if [ ! -e "${DTB_PATH}" ]; then
> + DTB_PATH="${B}/arch/${ARCH}/boot/${DTB}"
> + fi
> install -d ${DEPLOYDIR}
> - install -m 0644 ${B}/arch/${ARCH}/boot/${DTB} ${DEPLOYDIR}/${DTB_NAME}.dtb
> + install -m 0644 ${DTB_PATH} ${DEPLOYDIR}/${DTB_NAME}.dtb
The change looks fine to me.
Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Cheers,
Bruce
> cd ${DEPLOYDIR}
> ln -sf ${DTB_NAME}.dtb ${DTB_SYMLINK_NAME}.dtb
> cd -
>
prev parent reply other threads:[~2013-08-18 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 18:34 [PATCH] linux-dtb.inc: Fix dtb generation for kernels newer than 3.8 Otavio Salvador
2013-08-18 1:20 ` Bruce Ashfield [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=5210215B.5060908@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox