Re: [yocto] Strange bitbake error

On 2017-01-25 07:50, Gary Thomas wrote: For the last couple of days, I've been seeing my bitbake builds just shutdown, without actually completing, like this: Initialising tasks: 100% |###| Time: 0:00:10 NOTE: Executing SetScene

[yocto] Strange bitbake error

For the last couple of days, I've been seeing my bitbake builds just shutdown, without actually completing, like this: Initialising tasks: 100% |###| Time: 0:00:10 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks

[yocto] DISTRO_FEATURES vs IMAGE_FEATURES

Hello Yocto. Though it may feel to me matter of taste, is there suggestion on when which of these to use when you need to define your customized feature. DISTRO_FEATURES seems to be more relaxed, you can define things in your distro conf. IMAGE_FEATURE seems to be more strict, and you need to

Re: [yocto] [meta-raspberrypi][PATCH] u-boot: drop backported patches

On Tue, 24 Jan 2017 19:32:04 +0100 Mirza Krak wrote: > From: Mirza Krak > > U-boot has been updated to 2017.01 in poky/oe-core which contains > these patches. > > Signed-off-by: Mirza Krak I've been working on the exact same

Re: [linux-yocto] [linux-yocto-4.1] [Kernel-cache & bsp patch] Action-s500: Enable WIFI/BT/TPM support

On 01/22/2017 04:52 AM, Jiang Lu wrote: Hi Bruce, This series of patches enable support action s500 SOC and rose-apple-pi board. There are 95 patches for kernel to enable BT/WIFI/TPM feature on this board. I haven't forgotten about this, I'm just travelling and haven't had time to look at

[yocto] [meta-raspberrypi][PATCH] u-boot: drop backported patches

From: Mirza Krak U-boot has been updated to 2017.01 in poky/oe-core which contains these patches. Signed-off-by: Mirza Krak --- ...0001-arm-add-save_boot_params-for-ARM1176.patch | 56 ...through-of-the-firmware-provided-FDT-blob.patch |

Re: [yocto] Problems with building out-of-tree modules in morty

On 1/24/17 7:16 AM, Bogusz Brodziński wrote: > Hi, > > TL;DR after migrating from jethro to morty my out-of-tree modules do not > load. > > Long version: > Im developing uio driver for a custom FPGA. The base is xilinx zu15 > (note: as the explanation will go on I *think* it will be clear that

Re: [yocto] [layerindex-web] issue with webinterface

Right, we have not tested the layer index code with Django > 1.8.x, I would expect problems like this until we migrate (which probably won't be for a while I suspect). Cheers, Paul On Tuesday, 24 January 2017 2:57:46 PM NZDT Peter Tulpen wrote: > Hello Paul, > you are brilliant: > I had errors

[yocto] [meta-raspberrypi][morty][PATCH V2] Revert "u-boot: drop patch to include lowlevel_init"

From: Mirza Krak Not applicable on U-boot 2016.03 which is used in poky/morty and causes an build error when KERNEL_IMAGETYPE = "uImage". This reverts commit 031e26954b95d49a66ea4677b9e867d08441f450. [Issue #43] Signed-off-by: Mirza Krak ---

[yocto] [meta-raspberrypi][morty][PATCH] Revert "u-boot: drop patch to include lowlevel_init"

From: Mirza Krak Not applicaple on U-boot 2016.03 which is used in poky/morty. This reverts commit 031e26954b95d49a66ea4677b9e867d08441f450. [Issue #43] Signed-off-by: Mirza Krak --- .../0003-Include-lowlevel_init.o-for-rpi2.patch| 25

Re: [yocto] [layerindex-web][PATCH 2/2] views.py: Consider layer name in recipe search

ping On 01/18/2017 04:31 PM, Jose Lamego wrote: > From: Alex Franco > > Recipe search cannot be narrowed to a specific layer, producing > unnecessary results. > > This change allows including a layers name when searching for recipes to > narrow the yielded

Re: [yocto] [layerindex-web][PATCH 1/2] views.py: Redirect to recipe details for single results

ping On 01/18/2017 04:31 PM, Jose Lamego wrote: > From: Alex Franco > > When a recipe search returns only one result, clicking the single > result at the results view is still required to view further > recipe detail. > > This change automatically redirects to

Re: [yocto] [PATCH 0/7] introduce rockchip offical linux support to meta-rockchip

Hi Jacob, Sorry for the delay, I hadn't noticed the patches initially because the tag was missing, then I was busy with other things. I'm taking a look at them now. On Thu, Jan 19, 2017 at 10:17 AM, Leon Woestenberg wrote: > Hi Jacob, > > On Thu, Jan 19, 2017 at 11:09 AM,

[yocto] [patchwork][PATCH] parsemail: Set patch state from email metadata

Patch state can only be set/changed at patchwork web interface, resulting in a poor user experience for project maintainers. This change allows project maintainers to change a patch status directly from an email message sent as a reply to the related mailing list thread by including a the string

Re: [yocto] Ordering of anonymous Python functions and task signature calculations

On Tue, Jan 24, 2017 at 9:55 AM, Matt Hoosier wrote: > In order to support a use-case that embeds information about the Git > revision of Yocto itself that was used to make a build, I would like to run > some arbitrary Python code and dump the results (Git SHA1's, tag

[yocto] Ordering of anonymous Python functions and task signature calculations

In order to support a use-case that embeds information about the Git revision of Yocto itself that was used to make a build, I would like to run some arbitrary Python code and dump the results (Git SHA1's, tag names, etc) into a Bitbake variable. The idea is that the variable would get consumed

[yocto] Release Candidate Build for yocto-2.3_M2.rc1 now available.

A release candidate build for yocto-2.3_M2.rc1 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3_M2.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-qt4 : 2c7f8df9039be498f8a2232d1428adb7f4e5e800 meta-intel :

[yocto] Problems with building out-of-tree modules in morty

Hi, TL;DR after migrating from jethro to morty my out-of-tree modules do not load. Long version: Im developing uio driver for a custom FPGA. The base is xilinx zu15 (note: as the explanation will go on I *think* it will be clear that this is not related to meta-xilinx). It's basically a debug

[yocto] [PATCH 1/1] ref-manual: New SSHD_CONFIG variable description

Add description for the SSHD_CONFIG variable which is used to select the package to use as provider for sshd-config. Signed-off-by: David Vincent --- documentation/ref-manual/ref-variables.xml | 21 + 1 file changed, 21 insertions(+) diff --git

[yocto] [PATCH 0/1] Add SSHD_CONFIG variable description

Add the SSHD_CONFIG variable description to the glossary. This variable is introduced by the following patch series on OE-Core: https://patchwork.openembedded.org/series/4904 David Vincent (1): ref-manual: New SSHD_CONFIG variable description documentation/ref-manual/ref-variables.xml | 21

Re: [yocto] [layerindex-web] issue with webinterface

Hello Paul, you are brilliant: I had errors with django 1.10 and uncommented: from django.conf.global_settings import TEMPLATE_CONTEXT_PROCESSORS as TCP TEMPLATE_CONTEXT_PROCESSORS = TCP + ( 'django.core.context_processors.request', 'layerindex.context_processors.layerindex_context', )

Re: [yocto] SRC_URI patch slection

On 01/24/2017 06:37 AM, Takashi Matsuzawa wrote: In other words, in my iii) recipe I could say SRC_URI_remove = "file://.patch", but I want to make it only for specific SRCREV revisions. Or any other way of writing my iii) recipe for this? I would remove ii) altogether in the local layer

[yocto] SRC_URI patch slection

Hello. I have following recipe files and want to remove .patch added to SRC_URI at ii). i) _git.bb - specifies RC_URI revision by SRCREV parameter ii) _%.bbappend - adds several .patch to SRC_URI iii) _%.bbappend - my recipe I want to make it (removal) conditional to