[yocto] How to enable modules in kernel

Hi all, I'm trying to build for a raspberry pi3. I need to enable two drivers for sound devices: SND_SOC_MAX9768 & MAX1363. I've created my own image recipe and that is building. Now I need to add a couple of modules to the kernel configuration and I'm not sure what I need to do. Do I create a

Re: [linux-yocto] [linux-yocto-4.12][PATCH 1/1] ide:ide-cd: fix kernel panic resulting from missing scsi_req_init

On 2017-11-01 10:40 PM, Hongxu Jia wrote: Hi Bruce, The upstream accepted it, and merged to kernel 4.14. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79d73346ac05bc31f2e96f899c4e9616a8d4 For 4.12, we could not directly backport from 4.14, please merge

Re: [yocto] do_kernel_checkout() not using the correct directory

On 2017-11-02 4:16 PM, Bishop, Mark (STRT) wrote: I changed the code in arm/layers/core/meta/classes/kernel-yocto.bbclass From: . else     # case: we have no git repository at all. # To support low bandwidth options for building the kernel, we'll just    

Re: [yocto] [ptest-runner] utils.c: Prefer monotonic clock to calculate elapsed time

On 31/10/17 19:38, Jeffrey Pautler wrote: The current implementation uses the system clock to calculate how long a ptest has been running with no output. If a ptest changes the system clock as part of the test, that can cause the current implementation to falsely trigger a timeout or miss an

Re: [yocto] do_kernel_checkout() not using the correct directory

I changed the code in arm/layers/core/meta/classes/kernel-yocto.bbclass From: . else     # case: we have no git repository at all. # To support low bandwidth options for building the kernel, we'll just # convert the tree to a git repo and let the

[yocto] do_kernel_checkout() not using the correct directory

I am trying to compile a kernel located in SVN. I get this error message: ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: S /tmp/stride/work-shared/plnx_arm/kernel-source is not set to the linux source directory. Check ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0

Re: [yocto] Slightly varying builds

> On 02 November 2017 at 16:59 Alexander Kanavin > wrote: > > On 11/02/2017 06:50 PM, Colin Helliwell wrote: > > > > > u-boot-w2_1.inc has the standard kind of recipe stuff. For creating env > > files, and files to be used for later signing, it has some

Re: [yocto] Slightly varying builds

On 11/02/2017 06:50 PM, Colin Helliwell wrote: u-boot-w2_1.inc has the standard kind of recipe stuff. For creating env files, and files to be used for later signing, it has some _append steps, so I'm aiming to use 'DEP_IMG' to create the various files with different prefixes for the two

Re: [yocto] Slightly varying builds

> On 02 November 2017 at 16:29 Alexander Kanavin > wrote: > > On 11/02/2017 06:26 PM, Colin Helliwell wrote: > > > Following on from this, I'm trying to be able to build my two versions of > > u-boot, in the *same* build directory. > > I'm not sure if this

[yocto] Customize SDKPATH

Hello, As we build different images for the same machine, I would like to customize the SDKPATH to include the image name. This way our application developers can install the different sdk related to each image. To do that I firstly create my custom distro conf where I set the SDKPATH this way:

Re: [yocto] Slightly varying builds

On 11/02/2017 06:26 PM, Colin Helliwell wrote: Following on from this, I'm trying to be able to build my two versions of u-boot, in the *same* build directory. I'm not sure if this is possible, but I figured it might be: since u-boot doesn't get put into the rootfs (?), I would ideally be

Re: [yocto] Slightly varying builds

> On 02 November 2017 at 07:10 Colin Helliwell > wrote: > > > On 01 November 2017 at 17:04 Alexander Kanavin > > wrote: > > > > On 11/01/2017 06:43 PM, colin.helliw...@ln-systems.com wrote: > > > > > I need to build two

Re: [yocto] [meta-mono][PATCH] mono-4.xx: compiling mono 4 with btls requires cmake

On Thu, Nov 2, 2017 at 8:46 AM, Pascal Bach wrote: > > On 27.10.2017 23:41, Khem Raj wrote: >> On Fri, Oct 27, 2017 at 3:51 AM, Pascal Bach wrote: >>> This was probably working before pyro and the recipes specific sysroots. >>> >>> Signed-off-by:

Re: [yocto] [meta-raspberrypi][PATCH 1/5] x264: Disable asm for raspberrypi0-wifi

Hi all, On Thu, Nov 2, 2017 at 3:51 PM, Andrei Gherzan wrote: > This used to work in the past because this machine was based on raspberrypi > one. Now that they are separate, we need a configuration for it too > otherwise: > > | common/arm/quant-a.S: Assembler messages: > |

[yocto] [meta-raspberrypi][PATCH 5/5] firmware.in: Update to 20170811

Signed-off-by: Andrei Gherzan --- recipes-bsp/common/firmware.inc | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc index ac2bd82..67078c1 100644 --- a/recipes-bsp/common/firmware.inc

[yocto] [meta-raspberrypi][PATCH 4/5] rpi-base.inc: KERNEL_IMAGETYPE default to zzImage

We used to have this as the default but there was a bug at some point in the firmware which didn't work with compressed kernel images. We switched to Image and never changed it back even though that bug is long history. In this way we will stop carrying 15M of a kernel image. 4M looks much

[yocto] [meta-raspberrypi][PATCH 3/5] pi-blaster: An .inc file looks too much for this small recipe

Signed-off-by: Andrei Gherzan --- recipes-devtools/pi-blaster/pi-blaster.inc| 21 - recipes-devtools/pi-blaster/pi-blaster_git.bb | 22 +- 2 files changed, 21 insertions(+), 22 deletions(-) delete mode 100644

[yocto] [meta-raspberrypi][PATCH 2/5] linux-raspberrypi: Update 4.9 recipe to 4.9.59

Signed-off-by: Andrei Gherzan --- recipes-kernel/linux/linux-raspberrypi_4.9.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/recipes-kernel/linux/linux-raspberrypi_4.9.bb b/recipes-kernel/linux/linux-raspberrypi_4.9.bb index dd9afe2..061e893 100644

[yocto] [meta-raspberrypi][PATCH 1/5] x264: Disable asm for raspberrypi0-wifi

This used to work in the past because this machine was based on raspberrypi one. Now that they are separate, we need a configuration for it too otherwise: | common/arm/quant-a.S: Assembler messages: | common/arm/quant-a.S:362: Error: selected processor does not support `rbit r1,r1' in ARM mode |

Re: [yocto] [meta-mono][PATCH] mono-4.xx: compiling mono 4 with btls requires cmake

On 27.10.2017 23:41, Khem Raj wrote: > On Fri, Oct 27, 2017 at 3:51 AM, Pascal Bach wrote: >> This was probably working before pyro and the recipes specific sysroots. >> >> Signed-off-by: Pascal Bach >> --- >> recipes-mono/mono/mono-4.xx.inc |

Re: [yocto] Debugging a build issue in an isolated enviroment

Opa! Great command for the future, tnx. Strange that it isn't listed here and is greppable in bitbake -e u-boot-fw-utils-senic... Here it is: u-boot-fw-utils-senic-v2017.03+git999-r0 do_listtasks: do_build Default task for a recipe - depends on all other normal tasks required to

Re: [yocto] Debugging a build issue in an isolated enviroment

On 2 November 2017 at 13:31, Alan Martinovic wrote: > Found what I was asking for with: > > bitbake -e > > going through the output, there are mentions of patch_do_patch(). > I've traced it to meta/classes/patch.bbclass. > > However, trying to execute just the

Re: [yocto] Debugging a build issue in an isolated enviroment

Found what I was asking for with: bitbake -e going through the output, there are mentions of patch_do_patch(). I've traced it to meta/classes/patch.bbclass. However, trying to execute just the patching for the recipe doesn't work. build⟫ bitbake -c patch u-boot-fw-utils-senic ... ERROR: Task

Re: [yocto] Debugging a build issue in an isolated enviroment

That I can't see the changes for that particular patch in the source (by manually checking the source for the changes). Other patches are applied correctly, I can trace them in the sources. I have no "temp/log.do_patch" and find notions of patches (both the successfully and unsuccessfully applied

[yocto] [Yocto pyro] username adding via recipe in capital letters allowed?

Hi , I am using yocto pyro and for creating users via recipe using inherit useradd, followed http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-skeleton/recipes-skeleton/useradd/useradd-example.bb?h=pyro with lowercase I am able to create user e.g user as expected. but just want to check

Re: [yocto] Debugging a build issue in an isolated enviroment

What do you mean by patches not being applied correctly? temp/log.do_patch has the output from patch so that might show that you've a patch that applies with lots of fuzz and is applied incorrectly. Ross On 2 November 2017 at 11:46, Alan Martinovic wrote: > I see,

Re: [yocto] Debugging a build issue in an isolated enviroment

I see, so I can't use the devshell to debug why the patch hasn't been correctly applied. The answer you gave help for debugging actual build and configure problems. Debugging patching seems to be out scope for this thread. Will start a new one. On Thu, Nov 2, 2017 at 12:13 PM, Burton, Ross

Re: [yocto] Debugging a build issue in an isolated enviroment

The patching is done by a bbclass (patch.bbclass) and helper modules (meta/oe/lib/patch.py), so you can't execute it like a shell task (such as do_compile). Ross On 2 November 2017 at 11:05, Alan Martinovic wrote: > Thanks for the suggestions > Am currently

Re: [yocto] Debugging a build issue in an isolated enviroment

Thanks for the suggestions Am currently implementing both of them and am trying to understand how the patching is done. In the temp directory I can see all the tasks. For some reasons the patch wasn't applied correctly and I'm debugging why. I have patches from before which are being correctly

Re: [yocto] Slightly varying builds

> On 01 November 2017 at 17:04 Alexander Kanavin > wrote: > > On 11/01/2017 06:43 PM, colin.helliw...@ln-systems.com wrote: > > > I need to build two slightly varying versions of our Yocto build – one > > for the production units and one for development. > >

Re: [linux-yocto] [linux-yocto-4.12][PATCH 1/1] ide:ide-cd: fix kernel panic resulting from missing scsi_req_init

On 2017年11月02日 01:54, Bruce Ashfield wrote: Fixes: 82ed4db499b8 ("block: split scsi_request out of struct request") Upstream-Status: Submitted [linux-bl...@vger.kernel.org] I'll drop this during merge, but do you have a link to the mailing list archive for this ?