From: Esben Haabendal <eha@dev.doredevelopment.dk>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org, poky@yoctoproject.org, saul.wold@intel.com
Subject: Re: [PATCH 1/3] linux: factor dts/dtc/dtb handling into a specific include
Date: Thu, 10 Feb 2011 22:06:01 +0100 [thread overview]
Message-ID: <1297371961.3911.1.camel@eha> (raw)
In-Reply-To: <a80cd52437e3b3874ea0196d31127f14cf486f2f.1297232632.git.bruce.ashfield@windriver.com>
On Wed, 2011-02-09 at 01:27 -0500, Bruce Ashfield wrote:
> diff --git a/meta/recipes-kernel/linux/linux-dtb.inc b/meta/recipes-kernel/linux/linux-dtb.inc
> new file mode 100644
> index 0000000..0b27d18
> --- /dev/null
> +++ b/meta/recipes-kernel/linux/linux-dtb.inc
> @@ -0,0 +1,27 @@
> +# Support for device tree generation
> +FILES_kernel_devicetree = "/boot/devicetree*"
I guess that should be FILES_kernel-devicetree to actually match the
package name.
> +KERNEL_DEVICETREE_FLAGS = "-R 8 -p 0x3000"
> +
> +python __anonymous () {
> + import bb
> +
> + devicetree = bb.data.getVar("KERNEL_DEVICETREE", d, 1) or ''
> + if devicetree:
> + depends = bb.data.getVar("DEPENDS", d, 1)
> + bb.data.setVar("DEPENDS", "%s dtc-native" % depends, d)
> + packages = bb.data.getVar("PACKAGES", d, 1)
> + bb.data.setVar("PACKAGES", "%s kernel-devicetree" % packages, d)
> +}
> +
> +do_install_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
> + fi
> +}
> +
next prev parent reply other threads:[~2011-02-11 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 6:27 [PATCH 0/3] linux: factor dts/dtc/dtb handling into a specific include Bruce Ashfield
2011-02-09 6:27 ` [PATCH 1/3] " Bruce Ashfield
2011-02-10 21:06 ` Esben Haabendal [this message]
2011-02-11 10:27 ` Richard Purdie
2011-02-09 6:27 ` [PATCH 2/3] dtc: add LIC_FILES_CHKSUM to dtc-native Bruce Ashfield
2011-02-09 6:27 ` [PATCH 3/3] mpc8315-rdb: add dtb generation configuration Bruce Ashfield
2011-02-09 11:17 ` [PATCH 0/3] linux: factor dts/dtc/dtb handling into a specific include Richard Purdie
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=1297371961.3911.1.camel@eha \
--to=eha@dev.doredevelopment.dk \
--cc=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.org \
--cc=saul.wold@intel.com \
--cc=yocto@yoctoproject.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