[linux-yocto] [PATCH] common-pc-wifi: Enable SDIO for BroadCom BRCMFMAC

Enable Broadcom Wifi driver for SDIO mounted hardware on Intel boards Signed-off-by: Saul Wold --- Please apply to 4.9 and beyond. bsp/common-pc/common-pc-wifi.cfg | 3 +++ 1 file changed, 3 insertions(+) diff --git a/bsp/common-pc/common-pc-wifi.cfg

[yocto] [ARM][Renesas Salvator x Board R-car] PERF events support

Hello All , I want to ask if anyone managed to Run the PERF tool utilities that depends on the "perf events" as i have problem finding the path "/sys/kernel/debug/tracing/events" in my build even after configuring all the necessary options and recipes and many tries. some information about my

[yocto] Help With TEMPLATECONF & Automated Continuous Integration (CI)

Good morning, I am trying to setup an automate Jenkins CI server to build an image. To do this I need to automate the process of setting up the Yocto work area completely. As part of this process I am trying to eliminate the use of or automate the production of local.conf and bblayers.conf

Re: [linux-yocto] [kernel-cache][RFC PATCH 0/7] MicroBlaze and Zynq BSP configuration

On 2017-07-04 11:29 AM, Nathan Rossi wrote: Most of this configuration has existed in the meta-xilinx layer for quite some time for use with linux-yocto and Xilinx's vendor tree kernel, linux-xlnx. The goal is to enable the use of the MicroBlaze architecture in OE-Core including the addition of

Re: [linux-yocto] [kernel-cache][RFC PATCH 5/7] bsp/qemumicroblazeeb: Add BSP configs for qemumicroblazeeb

On 2017-07-04 11:29 AM, Nathan Rossi wrote: Create configs for the qemumicroblazeeb machine. This includes both -standard and -tiny configs. Signed-off-by: Nathan Rossi --- bsp/qemumicroblaze/qemumicroblazeeb-standard.scc | 15 +++

[yocto] RPi fails when build is with deb packages works okay with rpm packages.

Hello All,Does anyone know if recipes are available for gcc-arm-none-eabi & binutils-arm-none-eabi? My build works okay when I use package_rpm and fails with package_deb. My bblayers.conf & local.conf are at

Re: [yocto] Determining Load Addresses

Hi, On 2017-07-12 08:23, Kenny Koller wrote: I'm trying to piece together the various load addresses used in the boot sequence. I have built core-image-minimal for a Beaglebone. How can I determine which load address and entry point is used when mkimage is called for the kernel? Should I dig

[yocto] setting security attributes to device file(/dev/ipc)

Hello Team , I want to set ACL and SMACK/SELinux rules to device files (line /dev/ipc2 /dev/galcore etc .. ) from the build system . But device files are dynamically populated at runtime. Do we have some way in "Yocto" to achieve the goal ? Thanks & Regards Shrawan --

[yocto] Release Candidate Build for yocto-2.3.1.rc2 now available.

A release candidate build for yocto-2.3.1.rc2 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc2 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d meta-qt4 :

Re: [yocto] Release Candidate Build for yocto-2.3.1.rc1 now available

The RC2 e-mail should arrive shortly. It was sent the normal way, directly by the autobuilder. On Wed, Jul 12, 2017 at 10:03 AM, Perez Carranza, Jose < jose.perez.carra...@intel.com> wrote: > Hi Michael > > You sent the mail for rc1 and there is an rc2 available, according to RP > rc2 is the one

Re: [yocto] Release Candidate Build for yocto-2.3.1.rc1 now available

Hi Michael You sent the mail for rc1 and there is an rc2 available, according to RP rc2 is the one that will be used for QA. Regards, José -Original Message- From: Michael Halstead [mailto:mhalst...@linuxfoundation.org] Sent: Wednesday, July 12, 2017 11:38 AM To:

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

A release candidate build for yocto-2.3.1.rc1 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : 16aea09d224f3ed2021623d17c3e807f4b8ff18d meta-qt4 :