[yocto] FW: Yocto Project 1.4 release readiness meeting

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02000

[yocto] [yocto-autobuilder][RFC 6/6] CreateAutoConf.py: add option for package types

Using this option we'll be able to select only certain packages to be built and because the order is important we determine the image type too. E.g 'packages' : 'deb rpm' will build deb and rpm packages but the image will use deb as package manager. Signed-off-by: Stefan Stanacar --- .../site-pa

[yocto] [yocto-autobuilder][RFC 5/6] buildsteps/RunSanityTests.py: add suport for custom steps

Add an option so we can pass custom qemuimage tests, by appending TEST_SCEN to local.conf. This isn't used by any buildsets right now. It could be used when we want to run only certain sanity tests (i.e don't run all the tests in the image scenario but run only sanity:boot and sanity:dmesg by app

[yocto] [yocto-autobuilder][RFC 4/6] nightly.conf, yoctoAB.conf: enable the new buildsets

Add the new nightly-qa-extras and nightly-qa-systemd buildsets to the nightly target. Signed-off-by: Stefan Stanacar --- buildset-config/nightly.conf | 3 ++- buildset-config/yoctoAB.conf | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/buildset-config/nightly.conf b/build

[yocto] [yocto-autobuilder][RFC 3/6] buildset-config/nightly-qa-systemd.conf: add a new target for systemd images

Build systemd images in different configurations: systemd only, systemd+sysvinit and sysvinit+systemd (the order means which is the primary init system). Signed-off-by: Stefan Stanacar --- buildset-config/nightly-qa-systemd.conf | 20 1 file changed, 20 insertions(+) creat

[yocto] [yocto-autobuilder][RFC 2/6] CreateAutoConf.py: add initmgr option

Add an option to set the init manager used. This is used for building images with systemd. The order is important as it decides the primary one. Signed-off-by: Stefan Stanacar --- .../site-packages/autobuilder/buildsteps/CreateAutoConf.py | 13 + 1 file changed, 13 insertions(+) di

[yocto] [yocto-autobuilder][RFC 1/6] nightly-qa-extras.conf: add new buildset config

This buildset is for extra images which don't really fit in other buildsets. For now it includes builds for two images: one with btrfs and diffrent root home dir and a sato image with read-only rootfs. Signed-off-by: Stefan Stanacar --- buildset-config/nightly-qa-extras.conf | 16 +++

[yocto] [yocto-autobuilder][RFC 0/6] New buildsets and options for 1.5

Hello Beth, Would you mind taking a look on these changes? Obviously they are meant post-dylan release, but I sent them earlier so you can have time to review and request changes. It would be great to have them in 1.5 and I plan on adding even more builds (especially for multilib images and ipk

Re: [yocto] [eclipse-poky][RFC 0/6] Introducing a YoctoSDKCMakeProjectNature

Hi Atanas, Overall, the patches look good. Couple comments: 1. So from the end user perspective, after the 2nd patch set, user will see "Yocto Project ADT CMake Project" category when they want to create a new project? 2. Can we change the API for addNatures by using an enum type for projectNa

Re: [yocto] should i have known about "use-kernel-config"?

On Tue, 23 Apr 2013, Robert P. J. Day wrote: > > condensed version: i want to define a new machine for the MIPS > SEAD3, which is 32-bit, little endian, and it seemed pretty > straightforward, using the routerstation pro as a starting point and > making the appropriate tweaks. > > i chose to ba

[yocto] should i have known about "use-kernel-config"?

condensed version: i want to define a new machine for the MIPS SEAD3, which is 32-bit, little endian, and it seemed pretty straightforward, using the routerstation pro as a starting point and making the appropriate tweaks. i chose to base off of linux-yocto-3.8, and chose the standard/mti-mal

Re: [yocto] udev breakage

On 2013-04-23 04:34, Gary Thomas wrote: On 2013-04-22 17:09, Gary Thomas wrote: I've found that Poky/Yocto images built after this commit have a broken udev: commit c71d1f446c734954dceba0666c4f074047864b87 Author: Richard Purdie Date: Wed Apr 17 14:53:21 2013 + udev: Effectively re

[yocto] Building error for yocto

Hello, I have trying to build yocto for the past couple of days to test the hardware acceleration on the X11. However, when I try to build yocto I keep on getting this error: ERROR: Function failed: do_configure (see /home/lucid/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/busybox/1.2

[yocto] ADT development with makefiles

Hi, new to Yocto, I want to develop a software that runs when you start an overo gusmtix. I read the documentation but I still have many questions. If you can answer any of them you will be helping me a lot. I've built the gumstix-console-image

Re: [yocto] kernel-dev manual: SCC Description File Reference seems incomplete

On Tue, 23 Apr 2013, Bruce Ashfield wrote: > On 13-04-23 09:59 AM, Robert P. J. Day wrote: > > > >currently psyching up to work my way through the kernel dev manual, > > and i noticed this: > > > > http://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#scc-reference > > > > that re

Re: [yocto] kernel-dev manual: SCC Description File Reference seems incomplete

On 13-04-23 09:59 AM, Robert P. J. Day wrote: currently psyching up to work my way through the kernel dev manual, and i noticed this: http://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#scc-reference that reference list seems incomplete. at a *brief* glance: * no mention of

[yocto] kernel-dev manual: SCC Description File Reference seems incomplete

currently psyching up to work my way through the kernel dev manual, and i noticed this: http://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html#scc-reference that reference list seems incomplete. at a *brief* glance: * no mention of the "force" directive * no mention "include" dire

Re: [yocto] [PATCH] meta-jasperforest: Fix BBFILES

On Tue, 2013-04-23 at 13:26 +0100, Richard Purdie wrote: > BBFILES is whitespace delimited. If .= used, no whitespace padding is added > around > the addition and this can lead to it being combined with some other part of > the > field, leading to parts of BBFILES mysteriously not being seen. >

Re: [yocto] Splashscreen using psplash

On Tue, 2013-04-23 at 06:34 -0600, Gary Thomas wrote: > On 2013-04-23 06:29, Andreas Enbacka wrote: > > Hello, > > > > Thanks a lot for info, I will try with that. > > > > //Andreas > > > > -Original Message- > > From: Burton, Ross [mailto:ross.bur...@intel.com] > > Sent: 23. huhtikuuta 201

Re: [yocto] Splashscreen using psplash

On 2013-04-23 06:29, Andreas Enbacka wrote: Hello, Thanks a lot for info, I will try with that. //Andreas -Original Message- From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: 23. huhtikuuta 2013 15:09 To: Andreas Enbacka Cc: yocto@yoctoproject.org Subject: Re: [yocto] Splashscree

Re: [yocto] Splashscreen using psplash

Hello, Thanks a lot for info, I will try with that. //Andreas -Original Message- From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: 23. huhtikuuta 2013 15:09 To: Andreas Enbacka Cc: yocto@yoctoproject.org Subject: Re: [yocto] Splashscreen using psplash On 23 April 2013 13:03, Andr

[yocto] [PATCH] meta-jasperforest: Fix BBFILES

BBFILES is whitespace delimited. If .= used, no whitespace padding is added around the addition and this can lead to it being combined with some other part of the field, leading to parts of BBFILES mysteriously not being seen. For example, I have in my bblayers.conf: /media/build1/poky/meta-in

Re: [yocto] Splashscreen using psplash

On 23 April 2013 13:03, Andreas Enbacka wrote: > I am creating a custom image based on core-image-sato, with a custom splash > screen (using psplash). I have been able to replace the default yocto > splashscreen in my image, however, my question is whether it is possible to > hide the initial con

Re: [yocto] Splashscreen using psplash

On 2013-04-23 06:03, Andreas Enbacka wrote: Hello, I am creating a custom image based on core-image-sato, with a custom splash screen (using psplash). I have been able to replace the default yocto splashscreen in my image, however, my question is whether it is possible to hide the initial co

[yocto] Splashscreen using psplash

Hello, I am creating a custom image based on core-image-sato, with a custom splash screen (using psplash). I have been able to replace the default yocto splashscreen in my image, however, my question is whether it is possible to hide the initial console output text displayed on the screen prio

Re: [yocto] udev breakage

On 2013-04-22 17:09, Gary Thomas wrote: I've found that Poky/Yocto images built after this commit have a broken udev: commit c71d1f446c734954dceba0666c4f074047864b87 Author: Richard Purdie Date: Wed Apr 17 14:53:21 2013 + udev: Effectively revert the move to /sbin This effecti