Hi all,
This is latest Yocto bug trend chart for WW07. There were not so many bug fixing and submitting last week. Open bug number keeps around ~170.

Best Regards,
Jiajun

Hi Mark,
As Liping said, the following change breaks building xorg-minimal-fonts as destdir is not correct.
Can you please explain the actual different between cp and tar here? I think "cp -p" is similar to "tar -x -p" here?

@@ -706,17 +720,17 @@ class FetchMethod(object):
destdir = "."
elif not os.access("%s/%s" % (rootdir, destdir), os.F_OK):
os.makedirs("%s/%s" % (rootdir, destdir))
- cmd = 'cp -pPR %s %s/%s/' % (file, rootdir, destdir)
+ #cmd = 'cp -pPR %s %s/%s/' % (file, rootdir, destdir)
+ cmd = 'tar -cf - -C "%d" -ps . | tar -xf - -C "%s/%s/"' % (file, rootdir, destdir)


Thanks,
-- Dexuan

Hi, Mark

After fixing this typo, I found another error when bitbake xorg-minimal-fonts,
It will report
ERROR: Function 'org-minial-fonts: LIC_FILES_CHKSUM points to invalid file: ../misc/fonts/alias' failed

I checked the folder of build/tmp/work/all-poky-linux/xorg-minimal-fonts-1_1.0-r0, fonts.alias fonts.dir
Cursor.pcf.gz we not under misc subfolder as its expectation, but on the outer folder,
seems the SRC_URI="file://misc" defined in the Xorg-minimal-fonts.bb does not work.

Thanks a lot!
criping

Hi, all

Just found a small typo which caused built error today. The "%d" (file) should be changed to "%s", otherwise, compile error.

Anybody could help to modify the small bug if you're happening sending patches.

Thanks a lot for your help!
criping





author Mark Hatle <mark.hatle@...> 2011-02-11 17:43:54 (GMT)
committer Richard Purdie <richard.purdie@...> 2011-02-12 00:30:29 (GMT)
commit 3faa635fd408695dd5b754fda3f6060dd670b81d (patch) (side-by-side diff)
tree d0ba5d2d4acca9f7748029116f3a74877ee899c9
parent e56f63a2843e5a7d70fd60e0aaed4d962a277da7 (diff)
download poky-3faa635fd408695dd5b754fda3f6060dd670b81d.zip
poky-3faa635fd408695dd5b754fda3f6060dd670b81d.tar.gz
poky-3faa635fd408695dd5b754fda3f6060dd670b81d.tar.bz2



@@ -706,17 +720,17 @@ class FetchMethod(object):
destdir = "."
elif not os.access("%s/%s" % (rootdir, destdir), os.F_OK):
os.makedirs("%s/%s" % (rootdir, destdir))
- cmd = 'cp -pPR %s %s/%s/' % (file, rootdir, destdir)
+ #cmd = 'cp -pPR %s %s/%s/' % (file, rootdir, destdir)
+ cmd = 'tar -cf - -C "%d" -ps . | tar -xf - -C "%s/%s/"' % (file, rootdir, destdir)

On 11-02-11 5:59 PM, Chris Tapp wrote:

I'm trying to use 'menuconfig' to add a driver to the kernel.

I've been following the instructions I found at
http://groups.google.com/group/beagleboard/browse_thread/thread/7ebbfd2948579be0
that were posted by Frans Meulenbroeks. However, when I run

bitbake -c menuconfig virtual/kernel

I get

| Failed to parse arguments: Cannot open display:
| ERROR: Function 'do_menuconfig' failed (see ...

Any ideas? Only thing I can think is this is something to do with
ncurses...

It is this ?

http://bugzilla.pokylinux.org/show_bug.cgi?id=598

Bruce

Chris Tapp

opensource@...
www.keylevel.com



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto

I'm trying to use 'menuconfig' to add a driver to the kernel.

I've been following the instructions I found at http://groups.google.com/group/beagleboard/browse_thread/thread/7ebbfd2948579be0 that were posted by Frans Meulenbroeks. However, when I run

bitbake -c menuconfig virtual/kernel

I get

| Failed to parse arguments: Cannot open display:
| ERROR: Function 'do_menuconfig' failed (see ...

Any ideas? Only thing I can think is this is something to do with ncurses...

Chris Tapp

opensource@...
www.keylevel.com

On Thu, 2011-02-10 at 22:06 +0100, Esben Haabendal wrote:

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.

Yes, I've pushed a fix for that, thanks.

Richard

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
+}
+

I've noticed that poky@... and yocto@... both default to avoiding sending of duplicate mail. This is different to most other lists I subscribe to. By default it makes to me to allow users to perform their own filtering. Is there a reason we're disabling duplicates by default?

It is a per-user setting, so I was able to enable duplicates for my account.

--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Hello,

I thought I'd share the initial results from the documentation audit I've been doing.

I count a recipe as generating documentation if it creates a -doc output package which is populated with files (as opposed to an empty directory tree).

Using this metric, and building recipes as obtained from bitbake -s for qemux86, I've obtained the following numbers:

302 recipes are producing documentation
285 recipes do not currently produce documentation
22 recipes failed to build

I did manage to filter out from this analysis a number of obvious recipe filename patterns: task-/meta-/-native/-nativesdk/-image. That said, there are still some false negatives in the "documentation_missing" list. For example, our plethora of gcc-related recipes do not produce documentation and instead associate it with the primary recipe (gcc), and so on.

I will be continuing to look into fixing recipes with missing documentation that *should* be providing it as time goes on, but this gives us a good baseline to start with.

To keep track of this baseline, I will be coordinating with Saul sometime soon to add a new (Yocto is not a) distro tracking field to all recipes. This field will be named RECIPE_DOC_AUDIT_STATUS_pn-<pkg> and will be "red" for recipes that are either missing documentation or (as you add new recipes) have not been audited. The status will be "green" for recipes that either produce documentation or it's been confirmed that the recipe does not need to build documentation. I'd prefer not to further complicate the tracking field, but will consider suggestions from Saul or Richard if finer-grained detail is needed.

Scott

--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center

On Wed, Feb 9, 2011 at 6:14 AM, Richard Purdie
<richard.purdie@...> wrote:

On Wed, 2011-02-09 at 01:22 -0500, Bruce Ashfield wrote:

In order to build BSPs that were not already integrated into
the upstream linux yocto kernel AND keep the git fetcher happy,
some fairly complex anonymous python sections were required.

These sections cause problems with variable expansion and SRCREV
processing.

With the updated git fetcher code, we can streamline the BSP
boostrapping process and drop 99% of the anonymous python code.

This commit has the following changes to support BSP boot strapping
and simplication for existing BSPs.

   - KMETA is set per-recipe rather than in python code
   - undefined machines are no longer used, but instead common
     branch names are set per-recipe
   - fallback machine SRCREVs are present in the default revisions
     file
   - A new variable YOCTO_KERNEL_EXTERNAL_BRANCH should be set in
     the local.conf for new BSPs instead of being programatically
     determined in the anonymous python.
   - No more explicity KMACHINE variable expansion and manipulation,
     since the tools and build phases no longer require it due
     to the per-recipe fallbacks.

Integrated/merged BSPs are unaffected by the changes and have been
regression tested.

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>

diff --git a/meta/conf/distro/include/poky-default-revisions.inc b/meta/conf/distro/include/poky-default-revisions.inc
index 9abc4a5..a04fa9e 100644
--- a/meta/conf/distro/include/poky-default-revisions.inc
+++ b/meta/conf/distro/include/poky-default-revisions.inc
@@ -59,7 +59,7 @@ SRCREV_pn-gypsy ??= "147"
 SRCREV_pn-inputproto ??= "7203036522ba9d4b224d282d6afc2d0b947711ee"
 SRCREV_pn-inputproto-native ??= "7203036522ba9d4b224d282d6afc2d0b947711ee"
 SRCREV_pn-inputproto-nativesdk ??= "7203036522ba9d4b224d282d6afc2d0b947711ee"
-SRCREV_pn-kern-tools-native ??= "fde7ef8fa8043607752563b9b7908f487eb2f7dd"
+SRCREV_pn-kern-tools-native ??= "4f13a46499261ea181fdc13db5459067df08aca7"
 SRCREV_pn-libdrm ??= "3f3c5be6f908272199ccf53f108b1124bfe0a00e"
 SRCREV_pn-libfakekey ??= "e8c2e412ea4a417afc1f30e32cb7bdc508b1dccc"
 SRCREV_pn-libgdbus ??= "aeab6e3c0185b271ca343b439470491b99cc587f"
@@ -110,6 +110,7 @@ SRCREV_machine_pn-linux-yocto_mpc8315e-rdb ?= "68fb0b8d73bbb336ffa4a47bc70ec1eab
 SRCREV_machine_pn-linux-yocto_beagleboard ?= "343c06b25b221aa7f7019aee83b2d976041fddce"
 SRCREV_machine_pn-linux-yocto ?= "cb4faf3af527e25feee584f39c3956ca0c9448c8"
 SRCREV_meta_pn-linux-yocto ?= "5a32d7fe3b817868ebb697d2d883d743903685ae"
+SRCREV_machine_pn-linux-yocto ?= "cb4faf3af527e25feee584f39c3956ca0c9448c8"
 SRCREV_pn-linux-libc-headers-yocto ??= "343c06b25b221aa7f7019aee83b2d976041fddce"
 SRCREV_pn-matchbox-config-gtk ??= "3ed74dfb7c57be088a5ab36e446c0ccde9fa1028"
 SRCREV_pn-matchbox-desktop-sato ??= "76"
diff --git a/meta/recipes-kernel/linux/linux-yocto-stable_git.bb b/meta/recipes-kernel/linux/linux-yocto-stable_git.bb
index d4bee77..3c1e669 100644
--- a/meta/recipes-kernel/linux/linux-yocto-stable_git.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-stable_git.bb

I merged this with the exception of the second hunk above since it just
adds a duplicate line.

argh. Sorry about that, I was testing with your changes in my
tree and thought I had rebased them out!

Cheers,

Bruce

Cheers,

Richard

_______________________________________________
poky mailing list
poky@...
https://lists.yoctoproject.org/listinfo/poky

--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

On Wed, 2011-02-09 at 01:27 -0500, Bruce Ashfield wrote:

Richard/Saul,

This fixes BUGID 610, and kicks off a bit of cleaning with the various
kernel include files. Patch 1/3 says it all:

[
The powerpc linux-yocto kernels were not creating dtb images
in the deploy directories. This was due to two problems:

- the dtb generation rules were not being configured
- the boards were not specifying a device tree in their config

This change addresses the first point by factoring out the
dtb generation routines into a new include that can be used by
multiple recipes.
]

With these changes I've built and generated a dtb for the
mpc8315-rdb.

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/dtb
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/dtb

Looks good, merged to master, thanks.

Richard

On Wed, 2011-02-09 at 01:22 -0500, Bruce Ashfield wrote:

In order to build BSPs that were not already integrated into
the upstream linux yocto kernel AND keep the git fetcher happy,
some fairly complex anonymous python sections were required.

These sections cause problems with variable expansion and SRCREV
processing.

With the updated git fetcher code, we can streamline the BSP
boostrapping process and drop 99% of the anonymous python code.

This commit has the following changes to support BSP boot strapping
and simplication for existing BSPs.

- KMETA is set per-recipe rather than in python code
- undefined machines are no longer used, but instead common
branch names are set per-recipe
- fallback machine SRCREVs are present in the default revisions
file
- A new variable YOCTO_KERNEL_EXTERNAL_BRANCH should be set in
the local.conf for new BSPs instead of being programatically
determined in the anonymous python.
- No more explicity KMACHINE variable expansion and manipulation,
since the tools and build phases no longer require it due
to the per-recipe fallbacks.

Integrated/merged BSPs are unaffected by the changes and have been
regression tested.

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>

diff --git a/meta/conf/distro/include/poky-default-revisions.inc b/meta/conf/distro/include/poky-default-revisions.inc
index 9abc4a5..a04fa9e 100644
--- a/meta/conf/distro/include/poky-default-revisions.inc
+++ b/meta/conf/distro/include/poky-default-revisions.inc
@@ -59,7 +59,7 @@ SRCREV_pn-gypsy ??= "147"
SRCREV_pn-inputproto ??= "7203036522ba9d4b224d282d6afc2d0b947711ee"
SRCREV_pn-inputproto-native ??= "7203036522ba9d4b224d282d6afc2d0b947711ee"
SRCREV_pn-inputproto-nativesdk ??= "7203036522ba9d4b224d282d6afc2d0b947711ee"
-SRCREV_pn-kern-tools-native ??= "fde7ef8fa8043607752563b9b7908f487eb2f7dd"
+SRCREV_pn-kern-tools-native ??= "4f13a46499261ea181fdc13db5459067df08aca7"
SRCREV_pn-libdrm ??= "3f3c5be6f908272199ccf53f108b1124bfe0a00e"
SRCREV_pn-libfakekey ??= "e8c2e412ea4a417afc1f30e32cb7bdc508b1dccc"
SRCREV_pn-libgdbus ??= "aeab6e3c0185b271ca343b439470491b99cc587f"
@@ -110,6 +110,7 @@ SRCREV_machine_pn-linux-yocto_mpc8315e-rdb ?= "68fb0b8d73bbb336ffa4a47bc70ec1eab
SRCREV_machine_pn-linux-yocto_beagleboard ?= "343c06b25b221aa7f7019aee83b2d976041fddce"
SRCREV_machine_pn-linux-yocto ?= "cb4faf3af527e25feee584f39c3956ca0c9448c8"
SRCREV_meta_pn-linux-yocto ?= "5a32d7fe3b817868ebb697d2d883d743903685ae"
+SRCREV_machine_pn-linux-yocto ?= "cb4faf3af527e25feee584f39c3956ca0c9448c8"
SRCREV_pn-linux-libc-headers-yocto ??= "343c06b25b221aa7f7019aee83b2d976041fddce"
SRCREV_pn-matchbox-config-gtk ??= "3ed74dfb7c57be088a5ab36e446c0ccde9fa1028"
SRCREV_pn-matchbox-desktop-sato ??= "76"
diff --git a/meta/recipes-kernel/linux/linux-yocto-stable_git.bb b/meta/recipes-kernel/linux/linux-yocto-stable_git.bb
index d4bee77..3c1e669 100644
--- a/meta/recipes-kernel/linux/linux-yocto-stable_git.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-stable_git.bb

I merged this with the exception of the second hunk above since it just
adds a duplicate line.

Cheers,

Richard

Hi Bruce,

On Wed, 2011-02-09 at 01:22 -0500, Bruce Ashfield wrote:

The subject is a bit deceiving, since the 'streamlining' that I've been
working on for BSP / external board building for a while, actually
solves a lot of the SRCREV/race conditions that we've been seeing.

With the new fetcher and some factoring of the code, I've been able
to delete 99% of the anonymous python and simply the processing
for new BSPs.

To create a BSP against the yocto kernels all one must do is put
the variable YOCTO_KERNEL_EXTERNAL_BRANCH and indicate the branch
name that should be used. The tools and processing does the rest.

I built all existing boards, and bootstrapped a BSP against the
stable and devel yocto kernels while testing this. Everything
worked well.

Darren: I haven't touched the preempt_rt recipes (yet), but we
can streamline them as well.

This is the first step in some other refactoring and cleanups for
easier inclusion of the yocto kernel parts, but we'll let this
soak first before stacking more changes on top.

Looks good, nice to see this cleaning up, thanks! :)

Cheers,

Richard

Hi all,
This is latest Yocto bug trend chart for WW06. There were 24 bugs marked fixed last week. Now total open bug number decreased to 173.

Best Regards,
Jiajun

Fixes [BUGID #610]

dtb files were not being built for the mpc8315e-rdb, since they
weren't being configured into the machine. With this and the
related dtc fixes, we now get a dtb in the deployment directories.

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>
---
meta/conf/machine/mpc8315e-rdb.conf | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/meta/conf/machine/mpc8315e-rdb.conf b/meta/conf/machine/mpc8315e-rdb.conf
index ac518fb..578751c 100644
--- a/meta/conf/machine/mpc8315e-rdb.conf
+++ b/meta/conf/machine/mpc8315e-rdb.conf
@@ -17,3 +17,4 @@ PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"

UBOOT_ENTRYPOINT = "0x00000000"

+KERNEL_DEVICETREE = "${S}/arch/powerpc/boot/dts/mpc8315erdb.dts"
--
1.7.0.4

The new license processing rules error if dtc-native itself
doesn't have license information. Previously only the .inc
files contained this information, so we make a copy and leave
the existing license info to be removed pending further review.

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>
---
meta/recipes-kernel/dtc/dtc-native_git.bb | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/meta/recipes-kernel/dtc/dtc-native_git.bb b/meta/recipes-kernel/dtc/dtc-native_git.bb
index 2d6f092..fd5bde5 100644
--- a/meta/recipes-kernel/dtc/dtc-native_git.bb
+++ b/meta/recipes-kernel/dtc/dtc-native_git.bb
@@ -1,2 +1,5 @@
+LIC_FILES_CHKSUM = "file://GPL;md5=94d55d512a9ba36caa9b7df079bae19f \
+ file://libfdt/libfdt.h;beginline=3;endline=52;md5=fb360963151f8ec2d6c06b055bcbb68c"
+
require dtc-native.inc
require dtc_git.inc
--
1.7.0.4

Fixes [BUGID #610]

The powerpc linux-yocto kernels were not creating dtb images
in the deploy directories. This was due to two problems:

- the dtb generation rules were not being configured
- the boards were not specifying a device tree in their config

This change addresses the first point by factoring out the
dtb generation routines into a new include that can be used by
multiple recipes.

Signed-off-by: Bruce Ashfield <bruce.ashfield@...>
---
meta/recipes-kernel/linux/linux-dtb.inc | 27 +++++++++++++++++++++++++++
meta/recipes-kernel/linux/linux-yocto.inc | 1 +
meta/recipes-kernel/linux/linux.inc | 27 +--------------------------
3 files changed, 29 insertions(+), 26 deletions(-)
create mode 100644 meta/recipes-kernel/linux/linux-dtb.inc

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*"
+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
+}
+
diff --git a/meta/recipes-kernel/linux/linux-yocto.inc b/meta/recipes-kernel/linux/linux-yocto.inc
index 03935fa..0812144 100644
--- a/meta/recipes-kernel/linux/linux-yocto.inc
+++ b/meta/recipes-kernel/linux/linux-yocto.inc
@@ -18,5 +18,6 @@ addtask kernel_configme before do_configure after do_patch

# Pick up shared functions
inherit kernel-yocto
+require linux-dtb.inc

B = "${WORKDIR}/linux-${MACHINE}-${LINUX_KERNEL_TYPE}-build"
diff --git a/meta/recipes-kernel/linux/linux.inc b/meta/recipes-kernel/linux/linux.inc
index 93859bb..726d3d6 100644
--- a/meta/recipes-kernel/linux/linux.inc
+++ b/meta/recipes-kernel/linux/linux.inc
@@ -3,6 +3,7 @@ SECTION = "kernel"
LICENSE = "GPL"

inherit kernel
+require linux-dtb.inc

DEPENDS_append_em-x270 = " mtd-utils "

@@ -15,21 +16,6 @@ CMDLINE_at91sam9263ek = "mem=64M console=ttyS0,115200 root=/dev/mmcblk0p1 rootfs
#boot from nfs
#CMDLINE_at91sam9263ek = "mem=64M console=ttyS0,115200 root=301 root=/dev/nfs nfsroot=172.20.3.1:/data/at91 ip=172.20.0.5:::255.255.0.0"

-# Support for device tree generation
-FILES_kernel_devicetree = "/boot/devicetree*"
-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_configure_prepend() {
echo "" > ${S}/.config

@@ -105,14 +91,3 @@ do_install_prepend() {
fi
}

-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
-}
--
1.7.0.4

Richard/Saul,

This fixes BUGID 610, and kicks off a bit of cleaning with the various
kernel include files. Patch 1/3 says it all:

[
The powerpc linux-yocto kernels were not creating dtb images
in the deploy directories. This was due to two problems:

- the dtb generation rules were not being configured
- the boards were not specifying a device tree in their config

This change addresses the first point by factoring out the
dtb generation routines into a new include that can be used by
multiple recipes.
]

With these changes I've built and generated a dtb for the
mpc8315-rdb.

Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/dtb
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/dtb

Thanks,
Bruce Ashfield <bruce.ashfield@...>
---


Bruce Ashfield (3):
linux: factor dts/dtc/dtb handling into a specific include
dtc: add LIC_FILES_CHKSUM to dtc-native
mpc8315-rdb: add dtb generation configuration

meta/conf/machine/mpc8315e-rdb.conf | 1 +
meta/recipes-kernel/dtc/dtc-native_git.bb | 3 +++
meta/recipes-kernel/linux/linux-dtb.inc | 27 +++++++++++++++++++++++++++
meta/recipes-kernel/linux/linux-yocto.inc | 1 +
meta/recipes-kernel/linux/linux.inc | 27 +--------------------------
5 files changed, 33 insertions(+), 26 deletions(-)
create mode 100644 meta/recipes-kernel/linux/linux-dtb.inc