Re: [yocto] cannot build image using sstate

On Thu, 2017-03-09 at 08:54 +0200, Mircea Gliga wrote: > Long story short: I have problems building an image, in a clean build > directory, reusing the shared state cache and downloads from a previous > build. > A file created in the do_deploy_append task is not created(restored) > anymore when

Re: [yocto] hddimg 4GB limit?

Hello. I found hddimg 4GB-1 bye restriction because it creates a file called rootfs.img which is copied into FAT. That means rootfs.img size must be below FAT max file size... From: Takashi Matsuzawa Sent: Thursday, March 9, 2017 1:51 PM To:

[yocto] cannot build image using sstate

Long story short: I have problems building an image, in a clean build directory, reusing the shared state cache and downloads from a previous build. A file created in the do_deploy_append task is not created(restored) anymore when building using a previous sstate. And now the long

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

On 17-03-09 00:01:12, Trevor Woerner wrote: > On Wed 2017-03-08 @ 04:51:04 PM, Khem Raj wrote: > > On 17-03-08 19:01:05, Tom Rini wrote: > > > On Wed, Mar 08, 2017 at 03:42:00PM -0800, Khem Raj wrote: > > > > On 17-03-08 18:28:21, Tom Rini wrote: > > > > > On Wed, Mar 08, 2017 at 12:31:47PM -0500,

[yocto] hddimg 4GB limit?

Hello, Yocto. I have looked into hddimg file. According to image-live.bbclass, it is hardcoded to maximum 4GB size. But should not this more large? hddimg is generated by mkdosfs -F 32 that means the filesystem capacity is larger than 4GB. I just hit this limit when generating an image

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

On Wed 2017-03-08 @ 04:51:04 PM, Khem Raj wrote: > On 17-03-08 19:01:05, Tom Rini wrote: > > On Wed, Mar 08, 2017 at 03:42:00PM -0800, Khem Raj wrote: > > > On 17-03-08 18:28:21, Tom Rini wrote: > > > > On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote: > > > > > > > > >

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

On Wed 2017-03-08 @ 06:28:21 PM, Tom Rini wrote: Whoa! I didn't know I'd find you here :-) Bravo! > Unless there's an immediate need I would ask holding off on this for a > bit, I want to track down why this is happening. No problem. I really just want people to know I've found a work-around,

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

On 17-03-08 19:01:05, Tom Rini wrote: > On Wed, Mar 08, 2017 at 03:42:00PM -0800, Khem Raj wrote: > > On 17-03-08 18:28:21, Tom Rini wrote: > > > On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote: > > > > > > > openembedded-core updated bintuils from 2.27 to 2.28 which causes > > >

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel/yoctoAB.conf

Update yoctoAB.conf to reflect what is currently used in production and add nightly-musl and nightly-x32 builds to the configuration. Signed-off-by: Graydon, Tracy --- buildset-config.meta-intel/yoctoAB.conf | 11 +-- 1 file changed, 5 insertions(+), 6

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel/nightly-meta-intel.conf

Add the new nightly-musl and nightly-x32 builds to nightly-meta-intel build scheduler triggers. Signed-off-by: Graydon, Tracy --- buildset-config.meta-intel/nightly-meta-intel.conf | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel/nightly-x32.conf

Add nightly-x32 buildset with world build for meta-intel autobuilder. Signed-off-by: Graydon, Tracy --- buildset-config.meta-intel/nightly-x32.conf | 60 + 1 file changed, 60 insertions(+) create mode 100644

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel/nightly-musl.conf

Add nightly-musl buildset for meta-intel autobuilder. Signed-off-by: Graydon, Tracy --- buildset-config.meta-intel/nightly-musl.conf | 52 1 file changed, 52 insertions(+) create mode 100644 buildset-config.meta-intel/nightly-musl.conf

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

On Wed, Mar 08, 2017 at 03:42:00PM -0800, Khem Raj wrote: > On 17-03-08 18:28:21, Tom Rini wrote: > > On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote: > > > > > openembedded-core updated bintuils from 2.27 to 2.28 which causes u-boot > > > to > > > fail to compile: > > > > > >

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

On 17-03-08 18:28:21, Tom Rini wrote: > On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote: > > > openembedded-core updated bintuils from 2.27 to 2.28 which causes u-boot to > > fail to compile: > > > > arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for program > >

Re: [yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

On Wed, Mar 08, 2017 at 12:31:47PM -0500, Trevor Woerner wrote: > openembedded-core updated bintuils from 2.27 to 2.28 which causes u-boot to > fail to compile: > > arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for program > headers, try linking with -N > > Building with -N does

[yocto] [qa-tools][PATCH v2] testopia_update: Improvements on update action functionality

From: Jose Perez Carranza Some improvements were applied when using option action=create : - Create a new option to update test runs by ID - Create functions to load results and update test run - Add warning to use –testrun-id - Improvements to

Re: [yocto] [qa-tools][PATCH] testopia_update: Improvements on update action functionality

On 03/08/2017 09:56 AM, jose.perez.carra...@linux.intel.com wrote: > From: Jose Perez Carranza > > Some improvements were applied when using option > action=create : > >- Create a new option to update test runs by ID >- Create functions to load

[yocto] [meta-rockchip][PATCH] u-boot-rockchip: fix for binutils-2.28

openembedded-core updated bintuils from 2.27 to 2.28 which causes u-boot to fail to compile: arm-oe-linux-gnueabi-ld.bfd: u-boot: Not enough room for program headers, try linking with -N Building with -N does fix the issue, so this patch simply adds that flag to the build so it

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

On 8 March 2017 at 17:24, Dominig ar Foll (Intel Open Source) < dominig.arf...@fridu.net> wrote: > as now the recipe is called because I have declared that I wanted to use > vaapi. > It seems to call fo gst-plugins-bad. > > There is obviously quite a few problem with that recipe. >

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

Ross, as now the recipe is called because I have declared that I wanted to use vaapi. It seems to call fo gst-plugins-bad. There is obviously quite a few problem with that recipe. Regards. Dominig Le 08/03/2017 à

Re: [yocto] Raspberry Pi2 Fails to boot into LXDE.

On 17-03-08 12:40:51, Steve Plant wrote: > Hi All, > > > Very new to all this linux world, and especially Yocto. > > > I'm working on a embedded project at the moment using a raspberry pi2 board. > > > I have used toaster with Morty 2.2 to compile an image > using"rpi-basic-image", to this

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

On 17-03-08 15:44:08, Burton, Ross wrote: > On 8 March 2017 at 15:38, Burton, Ross wrote: > > > When 2.3 is released it won't be using the git gst-plugins-bad recipe by > > default either. I'll fix the recipe, but the git recipes are prone to > > breakage as they're not

[yocto] [qa-tools][PATCH] scripts: Wrapper that helps to create a full test cycle

From: Jose Perez Carranza Add a wrapper that helps to create the required test runs for a full cycle on master branch. Signed-off-by: Jose Perez Carranza --- scripts/full-test-cycle-wrapper.sh | 302

[yocto] [qa-tools][PATCH] testopia_update: Improvements on update action functionality

From: Jose Perez Carranza Some improvements were applied when using option action=create : - Create a new option to update test runs by ID - Create functions to load results and check missing test cases - Add warning to use –testrun-id -

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

On 8 March 2017 at 15:10, Dominig Ar Foll wrote: > yes, I now that I build the latest. > I am checking in advance of phase what will break in Automotive Grade > Linux (AGL) when 2.3 is coming out of the wood. > When 2.3 is released it won't be using the git

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

On 8 March 2017 at 15:38, Burton, Ross wrote: > When 2.3 is released it won't be using the git gst-plugins-bad recipe by > default either. I'll fix the recipe, but the git recipes are prone to > breakage as they're not that tested. > In fact the git recipes are actually

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

Ross, yes, I now that I build the latest. I am checking in advance of phase what will break in Automotive Grade Linux (AGL) when 2.3 is coming out of the wood. By the side, I also wants a 4.10 kernel for some test on virtualisation. Regards. Dominig Le 08/03/2017 à 15:33, Burton, Ross a écrit

Re: [yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

On 8 March 2017 at 14:29, Dominig ar Foll (Intel Open Source) < dominig.arf...@fridu.net> wrote: > ERROR: Task > (/home/dominig/AGL/poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_git.bb:do_patch) > failed with exit code '1' > > Are you aware that you're building the _git recipe

[yocto] gst-plugins-bad- Patch fails 'ensure-valid-sentinels-for-gst_structure_get-etc.patch'

For info. as the target file of this patch (gst-plugins-bad-1.10.2/sys/decklink/gstdecklink.cpp) has changed, the patch now fails when building yocto/maser It was created with gst-plugins-bad-1.10.2 but poky now download 1.10.4 the patch

[yocto] Raspberry Pi2 Fails to boot into LXDE.

Hi All, Very new to all this linux world, and especially Yocto. I'm working on a embedded project at the moment using a raspberry pi2 board. I have used toaster with Morty 2.2 to compile an image using"rpi-basic-image", to this I have added the following bitbake variables: Bitbake

[yocto] why is VOLATILE_LOG_DIR mentioned in ref manual when it doesn't exist?

not sure if i'm misreading this, but i note that an addition was made to the ref manual back in dec 2016: commit 5d2bdf49e569e44d02602501d72418f04dbe6e4a Author: Scott Rifenbark Date: Fri Dec 30 10:20:28 2016 -0800 ref-manual: New VOLATILE_LOG_DIR variable