Folks,
I'm trying to get devkit8000 kernel compiled with linux-yocto-stable recipe.
I've added devkit8000 on COMPATIBLE_MACHINE and on KMACHINE_dekvkit800.
But I don't know what pokylinux branch to use to make the kernel build
works.
I believe that I have to config these variables:
LINUX_KERNEL
On 11-02-08 08:46 AM, Diego Sueiro wrote:
Folks,
I'm trying to get devkit8000 kernel compiled with linux-yocto-stable recipe.
I've added devkit8000 on COMPATIBLE_MACHINE and on KMACHINE_dekvkit800.
But I don't know what pokylinux branch to use to make the kernel build
works.
I believe that I h
Dear Elizabeth Flanagan,
In message <4d4c9919.6060...@intel.com> you wrote:
>
> We are pleased to announce the first bug-fix release of Poky Laverne,
> 4.0.1. This release is available at:
>
> http://mirrors.kernel.org/yocto/poky/poky-laverne-4.0.1.tar.bz2
Is this Laverne 4.0.1 or 4.1 ? The git
Bruce,
I've updated my yocto tree but I'm still getting this error:
ERROR: Function 'do_kernel_checkout' failed (see
/home/dev-2/yocto/build/tmp/work/bw-b600-poky-linux-gnueabi/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_6+72ca49ab08b8eb475cec82a10049503602325791-r1/te
On 11-02-08 12:31 PM, Diego Sueiro wrote:
Bruce,
I've updated my yocto tree but I'm still getting this error:
ERROR: Function 'do_kernel_checkout' failed (see
/home/dev-2/yocto/build/tmp/work/bw-b600-poky-linux-gnueabi/linux-yocto-stable-2.6.34+git1+e1f85a470934a0cf6abde5d95533e74501822c6b_6+72
Bruce,
I'm getting this error for linux-libc-headers-yocto too.
ERROR: Function 'opkg-build execution failed' failed
ERROR: Logfile of failure stored in:
/home/dev-2/yocto/build/tmp/work/armv7a-poky-linux-gnueabi/linux-libc-headers-yocto-2.6.37+git-4+343c06b25b221aa7f7019aee83b2d976041fddce_2+yo
Bruce,
linux-libc-headers-yocto issue solved after yocto update.
Now, I'm waiting for linux-yocto-stable.
Regards,
--
*dS
Diego Sueiro
/*long live rock 'n roll*/
On Tue, Feb 8, 2011 at 4:04 PM, Diego Sueiro wrote:
> Bruce,
>
> I'm getting this error for linux-libc-headers-yocto too.
>
>
>
Richard/Saul,
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
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,
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 co
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 b
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
---
meta/recipes-kern
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
---
meta/conf/machine/mpc8315e-rdb.conf |1 +
1 fi
13 matches
Mail list logo
