[yocto] Add kernel path in *.bb file and Arm based board BSP

Hi All, I want to create a New BSP for ARM CorteXA9 based board . I have downloaded the poky 9.0.2 and create the new BSP with the following commands as mentioned in the Manual. "yocto-bsp create myarm arm" command and selected the "linux-Yocto_3.4" as my kernel.I hav

Re: [yocto] Custom defconfig is not used

On 13-10-17 11:47 AM, Diego Sueiro wrote: 2013/10/17 Bruce Ashfield mailto:bruce.ashfi...@windriver.com>> Look at oe-core/meta-skeleton for the custom kernel recipe example. It has the inherit/include combinations that you need to follow. My concern is: if doing this to just h

[yocto] how to enable the LTP in core-image-basic

Hi, I wants to use the LTP test suite provided by yocto project. But I don't know how to enable it for "core-image-basic". Can anyone help me to enable the LTP in "core-image-basic"? Thanks & Regards Amit K The contents of this e-mail and any attachme

[yocto] [PATCH] perf: fix bench numa compilation

From: Riccardo Magliocchetti Taken from: https://lkml.org/lkml/2013/6/20/80 Fix the following errors on gcc 4.8.1 / x86: bench/numa.c: In function worker_thread: bench/numa.c:1113:20: error: comparison between signed and unsigned integer expressions [-Werror=sign-compare] if (diff.tv_sec >

[yocto] [PATCH] lxc/namespace: Clean up kernel configs

Remove namespaces-experimental.cfg since USER_NS is not experimental anymore. Add CONFIG_USER_NS into namespaces.cfg. Add CONFIG_MACVLAN into lxc to avoid the below missing report from lxc-checkconfig: --- meta/cfg/kernel-cache/features/lxc/lxc.cfg | 3 ++- .../kernel-cac

Re: [yocto] [yocto-autobuilder] [PATCH 1/1] README-NEW-AUTOBUILDER: Add to scheduler documentation

Pulled into master. Thanks! -b On Mon, Oct 14, 2013 at 11:11 AM, Bryan Evenson wrote: > Adds detail on the Nightly scheduler properties that are > available. Notes default settings where appropriate and > notes which values must be set by the user. > > Signed-off-by: Bryan Evenson > --- > REA

Re: [yocto] [yocto-autobuilder][PATCH] buildsteps/CheckOutLayers: use a commit object for git rev-parse

Stefan, I'm pulling this patch, as this is part of our override of parseGotRevision in buildbot/steps/source/git.py, but I'd also suggest that this get suggested to the buildbot project for the original parseGotRevision. -b On Thu, Oct 10, 2013 at 6:18 AM, Stefan Stanacar wrote: > When the obje

Re: [yocto] Busybox configuration example?

On Thu, Oct 17, 2013 at 3:50 PM, Gary Thomas wrote: > Can someone explain how I might control my busybox builds? > For example, I routinely add this to busybox*.bbappend: > > # > # Force 'ifup' to wait longer for really slow links... > # > do_prepare_config_append () { > sed -i 's/CONF

[yocto] [meta-selinux][PATCH 4/5] Add packagegroup and image recipe for minimal SELinux image.

This is intended to demonstrate the minimal set packages necessary to boot and load a system with SELinux enabled. Specifically we don't need any of the packages that depend on python. --- .../images/core-image-selinux-minimal.bb | 15 +++ .../packagegroups/packagegroup-selinux

[yocto] [meta-selinux][PATCH 5/5] Add packagegroup for policycoreutils packages.

The policycoreutils package previously included most everything in the base package. This packagegroup is intended to fill the role of the old policycoreutils package and pull in all packages from the policycoreutils recipe. --- .../packagegroups/packagegroup-core-selinux.bb |4 +-- .../pa

[yocto] [meta-selinux][PATCH 3/5] Remove runtime dependency on policycoreutils from the reference policy.

The only thing refpol needs to depend on at runtime are the things necessary to load the policy. If sysvinit is patched to load the policy (which it is) then we only need the config. --- recipes-security/refpolicy/refpolicy_common.inc |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[yocto] [meta-selinux][PATCH 1/5] Break policycoreutils out into separate packages for the various utilities.

The driver beind this is to allow images to be built with the minimal tools necessary to load a policy. Breaking all of the stuff that's dependent on python out from the core utils allows us to make much smaller images. --- recipes-security/selinux/policycoreutils.inc | 181 +

[yocto] [meta-selinux][PATCH 0/5] Resend: Remove python dependency from refpol.

This is a resend of an earlier patch set that never made it to the list AFAIK. The reference policy package currently pulls in a lot of python stuff that isn't strictly necessary to boot an SELinux system and load a policy. AFAIK this is caused by the mix of python and C utilities in policycoreuti

[yocto] [meta-selinux][PATCH 2/5] Remove unnecessary RDEPENDS_${BPN}.

Now that the policycoreutuils package is empty no need for RDEPENDS. Doing this in the commit that broke up the policycoreutuils package made the diff hard to read. Figured it best to break it out for readability. --- recipes-security/selinux/policycoreutils.inc | 16 1 file cha

Re: [yocto] meta-xilinx

On Oct 17, 2013, at 8:05 AM, Edward Vidal wrote: > Hello, > I got the following error. > DEBUG: Executing shell function do_compile > NOTE: make -C > /home/vidal/POKY/build101613_zedboard/poky/build/tmp/sysroots/zedboard-zynq7/usr/src/kernel/tools/perf > > O=/home/vidal/POKY/build101613_zedbo

Re: [yocto] meta-xilinx

This is may be better asked on the meta-xilinx list: https://lists.yoctoproject.org/listinfo/meta-xilinx Philip On 10/17/2013 11:05 AM, Edward Vidal wrote: > Hello, > I got the following error. > DEBUG: Executing shell function do_compile > NOTE: make -C > /home/vidal/POKY/build101613_zedboard/p

Re: [yocto] Custom defconfig is not used

2013/10/17 Bruce Ashfield > Look at oe-core/meta-skeleton for the custom kernel recipe example. > It has the inherit/include combinations that you need to follow. > > > My concern is: if doing this to just have the config fragment feature, >> I'll possibly mess up the kernel build. >> > > It sho

Re: [yocto] Busybox configuration example?

On 17/10/13 14:50, Gary Thomas wrote: > I see mention of busybox configuration fragments in the mega > manual (section 5.9.7) but no explanation nor examples. > > Can someone explain how I might control my busybox builds? > For example, I routinely add this to busybox*.bbappend: > > # > # For

Re: [yocto] meta-xilinx

Hello, I got the following error. DEBUG: Executing shell function do_compile NOTE: make -C /home/vidal/POKY/build101613_zedboard/poky/build/tmp/sysroots/zedboard-zynq7/usr/src/kernel/tools/perf O=/home/vidal/POKY/build101613_zedboard/poky/build/tmp/work/zedboard_zynq7-poky-linux-gnueabi/perf/1.0-r8

Re: [yocto] Custom defconfig is not used

On Thu, Oct 17, 2013 at 3:19 PM, Bruce Ashfield wrote: > On 13-10-17 09:15 AM, Diego Sueiro wrote: >> >> >> 2013/10/17 Bruce Ashfield > > >> >> >> >> >> I expected to get this working "out-of-box". >> >> >> Did you do a "bitbake -e " ? and then loo

[yocto] Busybox configuration example?

I see mention of busybox configuration fragments in the mega manual (section 5.9.7) but no explanation nor examples. Can someone explain how I might control my busybox builds? For example, I routinely add this to busybox*.bbappend: # # Force 'ifup' to wait longer for really slow links... #

Re: [yocto] default root password

2013/10/17 Bryan Evenson > I know there is the EXTRA_USER_PARAMS feature for adding users and > modifying a user's password, but I couldn't get it to work for root. I > tried adding: > > INHERIT += "extrausers" > EXTRA_USERS_PARAMS = "\ > usermod -p '' root; \ > " > > and I would get err

Re: [yocto] default root password

David, I've had similar issues, and this is what I've done to get the root password set properly in my image. I am using poky/Dylan-9.0.1 for a starting point. 1. In my case, I want a root password that is longer than 8 characters. With poky/dylan, it is using tinylogin for password managemen

Re: [yocto] Custom defconfig is not used

On 13-10-17 09:15 AM, Diego Sueiro wrote: 2013/10/17 Bruce Ashfield mailto:bruce.ashfi...@windriver.com>> I expected to get this working "out-of-box". Did you do a "bitbake -e " ? and then look at the SRC_URI ? That will tell us if for some reason the beagle layer's def

Re: [yocto] Custom defconfig is not used

2013/10/17 Bruce Ashfield > > > I expected to get this working "out-of-box". >> > > Did you do a "bitbake -e " ? and then look at > the SRC_URI ? That will tell us if for some reason the beagle layer's > defconfig is on there twice. I'll do it after my current build gets finished. > > > Wh

Re: [yocto] Custom defconfig is not used

On 13-10-17 06:39 AM, Diego Sueiro wrote: 2013/10/17 Bruce Ashfield mailto:bruce.ashfi...@gmail.com>> On Wed, Oct 16, 2013 at 2:19 PM, Diego Sueiro mailto:diego.sue...@gmail.com>> wrote: > Folks, > > Looking at log.do_unpack it shows: > > ... > NOTE: Unpa

Re: [yocto] default root password

2013/10/16 David Andrey > Hi, > > There are lot of threads floating around, and a FAQ without answer. > https://wiki.yoctoproject.org/wiki/FAQ:How_do_I_set_or_change_the_root_p > assword > > So what is the official way to set a default root password ? > Using a sed command on /etc/passwd through

Re: [yocto] Custom defconfig is not used

2013/10/17 Bruce Ashfield > On Wed, Oct 16, 2013 at 2:19 PM, Diego Sueiro > wrote: > > Folks, > > > > Looking at log.do_unpack it shows: > > > > ... > > NOTE: Unpacking > > > <...>/meta-beagleboard/common-bsp/recipes-kernel/linux/linux-mainline-3.8/beaglebone/defconfig > > to > > > <...>/build/t