[yocto] Reminder: Yocto Project Technical Team Meeting - Tuesday, Feb. 2, 2016 8:00 AM US Pacific Time

Tuesday, Feb. 2, 2016 8:00 AM US Pacific Time Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule https://wiki.yoctoproject.org/wiki/Yo

Re: [yocto] network drivers are not installed when MACHINE qemux86-64

On Mon, Feb 1, 2016 at 8:48 PM, Nathan Sowatskey wrote: > As a follow up, I have just done this: > > bitbake core-image-kernel-dev > > And now I get the eth0 interface configured and active when I start the Yocto > image. > > I do not have to configure and start it manually. Can you check if rel

Re: [yocto] network drivers are not installed when MACHINE qemux86-64

As a follow up, I have just done this: bitbake core-image-kernel-dev And now I get the eth0 interface configured and active when I start the Yocto image. I do not have to configure and start it manually. Regards Nathan > On 1 Feb 2016, at 13:31, Nathan Sowatskey wrote: > > Hi > > I think

[yocto] Problem installing ath10k firmware

Hello, We're having a problem getting the ath10k firmware to run with a new wireless card. The card uses chip QCA9882. We've tried installing ath10k firmware using: IMAGE_INSTALL_append += linux-firmware-ath10k in combination with the following kernel configs: CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_

Re: [yocto] Compiling different version of IGB as a kernel module

Got it figured out. Turns out I needed some more changes to the Makefile. New patch attached in case anyone is interested. Bottom line is that the CC command was getting forcibly set at some point to check compilers, thus overriding the shell setting. Plus it needed a modules_install as well

Re: [yocto] Missing task queue dependencie while building qt5-image-demo: SAMBA

http://layers.openembedded.org/layerindex/branch/master/recipes/?q=samba you need to add meta-oe layer to your setup. On Mon, Feb 1, 2016 at 8:53 PM, Karim ATIKI wrote: > Hi, > > > I recently upgrade all my yocto tree to jethro. > > > Attempting to build qt5-image-demo recipe from meta-qt5, I g

Re: [yocto] Password updates to compressed root image in flash

> On Feb 1, 2016, at 3:47 AM, David Bilsby wrote: > > We have a project which will use a Xilinx Zynq running embedded Linux built > by Yocto (probably kernel 4.0). The system will boot from QSPI, this will > contain the FSBL, u-boot, compressed kernel and compressed rootfs. The rootfs > will

Re: [yocto] Migrate, or not Migrate, that's the question!!!

> On Feb 1, 2016, at 6:18 AM, Diego Sueiro wrote: > > Bryan, > > > On 28 January 2016 at 13:49, Bryan Evenson > wrote: > In my opinion, I think in the long term it would be easier to make a clean > break. Start with a recent branch, like Jethro, get a minimal

Re: [yocto] [meta-security-rockwell] Introduction of a new OE layer: help in hardening your Yocto daisy built systems

> On Feb 1, 2016, at 8:46 AM, Ben Gardiner wrote: > > We would like to introduce a new layer: meta-security-rockwell > > We’ve built on other excellent projects to realize this layer (so far) and > have relied on help from many of you on IRC. Thank you. > > Our goal is to support the daisy re

Re: [yocto] Glibc 2.24 _might_ require minimum kernel version 3.2

On Mon, Feb 1, 2016 at 10:10 AM, akuster wrote: > > > On 01/31/2016 09:41 AM, Khem Raj wrote: >> Hi >> >> This is FYI, as I have sent a RFT for glibc 2.24, there might be another >> change >> coming which is under discussion on glibc mailing lists which is on >> supported minimum >> kernel versio

Re: [yocto] Glibc 2.24 _might_ require minimum kernel version 3.2

On 01/31/2016 09:41 AM, Khem Raj wrote: > Hi > > This is FYI, as I have sent a RFT for glibc 2.24, there might be another > change > coming which is under discussion on glibc mailing lists which is on > supported minimum > kernel version bump to 3.2 since 2.6.32 will be EOLed this summer [1] >

[yocto] [meta-security-rockwell] Introduction of a new OE layer: help in hardening your Yocto daisy built systems

We would like to introduce a new layer: meta-security-rockwell We’ve built on other excellent projects to realize this layer (so far) and have relied on help from many of you on IRC. Thank you. Our goal is to support the daisy release of Yocto and to (eventually) require explicit skipping of wa

Re: [yocto] Migrate, or not Migrate, that's the question!!!

Bryan, On 28 January 2016 at 13:49, Bryan Evenson wrote: > In my opinion, I think in the long term it would be easier to make a clean > break. Start with a recent branch, like Jethro, get a minimal image to > build for your hardware and then add your own layer with your proprietary > recipes.

Re: [yocto] network drivers are not installed when MACHINE qemux86-64

Hi I think I am seeing something similar. I only have video in my kernel/drivers directory, which is to say that there is no net directory either. I have been using the Build Appliance to create a qemux86-64 core-image-full-cmdline machine. When I ran that without any -netdev arguments at all,

[yocto] Password updates to compressed root image in flash

We have a project which will use a Xilinx Zynq running embedded Linux built by Yocto (probably kernel 4.0). The system will boot from QSPI, this will contain the FSBL, u-boot, compressed kernel and compressed rootfs. The rootfs will be expanded into an initramfs which will then be used as the r

Re: [yocto] How to get the latest version of Qt5 with meta-qt5

Hi, In the meta-qt5 repo on github : fido branch is Qt 5.4 jethro branch is Qt 5.5 master branch is Qt 5.6 a simple "git checkout -b jethro" should get you there... Le lun. 1 févr. 2016 à 09:56, Martin Jansa a écrit : > On Mon, Feb 01, 2016 at 08:39:08AM +, Karim ATIKI wrote: > > Hi all

Re: [yocto] How to get the latest version of Qt5 with meta-qt5

On Mon, Feb 01, 2016 at 08:39:08AM +, Karim ATIKI wrote: > Hi all, > > > I've been using yocto to create distros on rspi2 and develop Qt5 based > applications. > > > I noticed that through the meta-qt5 layer, it is Qt 5.4.1 that is compiled > and deployed. I don't know how you noticed th