Re: [yocto] Automating imaging building and testing, what aproach to use!?

On 2016-08-30 04:18 PM, Daniel. wrote: Hey everybody! While writing software we're used to delivery packages, libraries and stacks. There are out there a lot of continuos integration solutions to automatically build and test these kinds of software. But when dealing to images the thing is more

Re: [yocto] [layerindex-web][PATCH 0/3] Layer index fixes

On Tue, Aug 30, 2016 at 11:03 PM, Paul Eggleton wrote: > Some minor fixes for the recent python3 work in the layer index, but more > importantly fix parsing in master for the multiconfig changes that recently > went into bitbake. > > NOTE: this depends on the

[yocto] [layerindex-web][PATCH 3/3] update_layer.py: fix up for bitbake API change

The multiconfig changes broke the calls here to loadDataFull(). To avoid this being an issue in future, make use of tinfoil's new parse_recipe_file() function (if available) to isolate the code here from any future changes to bitbake's internal code. Part of the fix for [YOCTO #10192].

[yocto] [layerindex-web][PATCH 1/3] Use python3 commands in README

If you're in a virtualenv it doesn't make a difference, but outside of one it will. Signed-off-by: Paul Eggleton --- README | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README b/README index fa5c3b2..8437089 100644 --- a/README +++

[yocto] [layerindex-web][PATCH 2/3] Fix output decoding/reporting for bulk change patch download

With Python 3 we need to take care of decoding the output so we can treat it as a string. At the same time, it's more useful to see the output string rather than the exception if there is some output. Signed-off-by: Paul Eggleton --- layerindex/views.py | 3 +++ 1

[yocto] [layerindex-web][PATCH 0/3] Layer index fixes

Some minor fixes for the recent python3 work in the layer index, but more importantly fix parsing in master for the multiconfig changes that recently went into bitbake. NOTE: this depends on the bitbake patchset I just sent in order to work. The following changes since commit

[yocto] Automating imaging building and testing, what aproach to use!?

Hey everybody! While writing software we're used to delivery packages, libraries and stacks. There are out there a lot of continuos integration solutions to automaticaly build and test these kinds of software. But when dealing to images the thing is more tricky. I can't run the tests at the same

Re: [yocto] [PATCH][yocto-autobuilder] nightly-qa-systemd.conf: Add create_eventlog property

On Aug 30, 2016 8:46 AM, "Aníbal Limón" wrote: > > This buildset also needs the create_eventlog property for only > enable the toaster event log creation when required. See rev [1]. > > [1] 0b083509beaf7421f1dde4b679a934741ac4a3bc > > Signed-off-by: Aníbal Limón

[yocto] [PATCH][yocto-autobuilder] nightly-qa-systemd.conf: Add create_eventlog property

This buildset also needs the create_eventlog property for only enable the toaster event log creation when required. See rev [1]. [1] 0b083509beaf7421f1dde4b679a934741ac4a3bc Signed-off-by: Aníbal Limón --- buildset-config.controller/nightly-qa-systemd.conf | 4

Re: [yocto] [meta-swupd][PATCH v2] swupd-client_git.bb: Make pinned pubkey configurable

On Mon, 2016-08-29 at 11:09 +0300, Dmitry Rozhkov wrote: > SWUPD server may move to a new location where a different pubkey > needs to be used and the hardcoded one won't work. > > This makes pinned pubkey configurable. Thanks Dmitry, patch pushed. Regards, Joshua > > Changes in v2: add

[yocto] Problem with exporting variable in bbappend file

Hello all, We are working on a platform based on Renesas processor. The BSP provided by them has arm-trusted-firmware. Now in order to enable all the 8 cores, they have suggested to add a environment variable in the arm-trusted-firmware_git.bb file in their BSP layer as below. export

Re: [yocto] custom linux kernel recipe

On 2016-08-30 07:33 AM, Mircea Gliga wrote: Thanks for your answer Bruce ! I've applied the patch you've mentioned (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=zedd/kernel=0fe665e69983fe9ef38319deedcb78ecd7b165cf) to my recipe, linux-stable_4.7.bb, providing the dtb:

Re: [yocto] custom linux kernel recipe

Thanks for your answer Bruce ! I've applied the patch you've mentioned (http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=zedd/kernel=0fe665e69983fe9ef38319deedcb78ecd7b165cf) to my recipe, linux-stable_4.7.bb, providing the dtb: KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"

[yocto] Building kernel with non standard source structure

Hello, I'm trying to port the kernel compilation of a bsp to yocto. My problem is that this kernel has a bunch of drivers that are out of the kernel sources tree and all the includes are hard coded with an uncommon structure. To give you the idea, the source is organized in this way