[yocto] meta-zephyr layer

There is interest in the community to support building Zephyr images ( https://www.zephyrproject.org/ )in Yocto via bitbake recipes. AFAIK the only way thus far to build Zephyr images is based on command line/Kconfig, similar to building Linux kernel images. Building of Zephyr images in Yocto

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-base.bbclass: remove version hack

2016-12-12 06:21 skrev Khem Raj: > On Thu, Dec 8, 2016 at 2:40 AM, Andreas Müller > wrote: > >> * no more required (version > 3.17 | > 4.3.x | > 4.4.5) * causes error with rt kernel > > I think this is ok to apply now. > >> Signed-off-by: Andreas Müller

Re: [yocto] meta-zephyr layer

you need poky to build QEMUs and toolchains > -Original Message- > From: Philip Balister [mailto:phi...@balister.org] > Sent: Monday, December 12, 2016 2:19 PM > To: Bystricky, Juro ; yocto@yoctoproject.org > Subject: Re: [yocto] meta-zephyr layer > > Does that

Re: [yocto] meta-zephyr layer

On 12 December 2016 at 22:52, Bystricky, Juro wrote: > you need poky to build QEMUs and toolchains > You should just need *OpenEmbedded* to build the qemus and toolchains. Why does zephyr.conf include poky.conf? I'd say that any variables that are useful - such as

Re: [yocto] meta-zephyr layer

Does that work without poky? Philip On 12/12/2016 02:15 PM, Bystricky, Juro wrote: > There is interest in the community to support building Zephyr images > ( https://www.zephyrproject.org/ )in Yocto via bitbake recipes. > AFAIK the only way thus far to build Zephyr images is based on command >

Re: [yocto] Kernel config incremental modification not working.

On Mon, 12 Dec 2016 08:41:36 Bruce Ashfield wrote: > On 2016-12-11 02:33 PM, Paul Eggleton wrote: > > Can we please have some automated tests covering all of this? Perhaps it > > would be worth talking to Francisco Pedraza who is looking at adding > > tests under bug > > 6359: > > We are already

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-base.bbclass: remove version hack

On Mon, Dec 12, 2016 at 11:33 PM, Petter Mabäcker wrote: > 2016-12-12 06:21 skrev Khem Raj: > > On Thu, Dec 8, 2016 at 2:40 AM, Andreas Müller > wrote: > > * no more required (version > 3.17 | > 4.3.x | > 4.4.5) * causes error with > rt kernel > >

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-base.bbclass: remove version hack

2016-12-13 00:55 skrev Andreas Müller: > On Mon, Dec 12, 2016 at 11:33 PM, Petter Mabäcker wrote: > >> 2016-12-12 06:21 skrev Khem Raj: On Thu, Dec 8, 2016 at 2:40 AM, Andreas Müller wrote: * no more required (version > 3.17 | > 4.3.x | >

[yocto] [PATCH v2] ref-manual: New WKS_FILE variable glossary entry.

Signed-off-by: Ed Bartosh --- documentation/ref-manual/ref-variables.xml | 14 ++ 1 file changed, 14 insertions(+) diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index 4e003cd..9c03364 100644 ---

[yocto] [meta-raspberrypi][PATCH 1/2] rpi-base.inc: add xserver-xorg-extension-glx to XSERVER for vc4 enabled

make glxinfo/glggears/.. work Signed-off-by: Andreas Müller --- conf/machine/include/rpi-base.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/machine/include/rpi-base.inc b/conf/machine/include/rpi-base.inc index 497dd29..9ce647d 100644 ---

[yocto] [meta-raspberrypi][PATCH 2/2] rpi-base.inc: remove input modules form XSERVER

This is nothing a BSP has to decide Signed-off-by: Andreas Müller --- conf/machine/include/rpi-base.inc | 3 --- 1 file changed, 3 deletions(-) diff --git a/conf/machine/include/rpi-base.inc b/conf/machine/include/rpi-base.inc index 9ce647d..9f20663 100644 ---

Re: [yocto] Kernel config incremental modification not working.

On 2016-12-11 02:33 PM, Paul Eggleton wrote: On Fri, 09 Dec 2016 11:19:56 Bruce Ashfield wrote: On 2016-12-09 11:17 AM, Andrea Galbusera wrote: Hi Bruce, On Thu, Dec 8, 2016 at 3:36 PM, Bruce Ashfield > wrote: On

Re: [yocto] update mechanisms

>> I >> tried to summarize the key aspects of each mechanism in the table >> itself. That's something that I haven't seen elsewhere and something >> that the page can I tried to be as fair and objective as possible, >> please shout if I messed something up or you don't agree with my >> summary.

[yocto] suggestions for version controlling multi-layer reproducible builds?

(if there's already a doc section for this somewhere, a pointer to it would be just ducky.) if one is building an image for a releasable, commercial product, and that image involves pulling in numerous layers, then dumping all sorts of proprietary apps on top of it, what are the

Re: [yocto] update mechanisms

Hi, On Tue, 2016-12-06 at 10:45 +0100, Patrick Ohly wrote: > On Tue, 2016-12-06 at 10:01 +0100, Stefano Babic wrote: > > Hi Patrick, > > > > On 30/11/2016 15:59, Patrick Ohly wrote: > > > I've started a Wiki page > > > https://wiki.yoctoproject.org/wiki/System_Update - rudimentary at the > > >

Re: [yocto] suggestions for version controlling multi-layer reproducible builds?

On Mon, Dec 12, 2016 at 8:20 AM, Robert P. J. Day wrote: > if one is building an image for a releasable, commercial product, > and that image involves pulling in numerous layers, then dumping all > sorts of proprietary apps on top of it, what are the possibilities for >

Re: [yocto] Can't enable reverse debugging

> -Original Message- > From: Khem Raj [mailto:raj.k...@gmail.com] > Sent: Monday, December 12, 2016 2:54 PM > To: Bryan Evenson > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Can't enable reverse debugging > > > > On Dec 12, 2016, at 11:12 AM, Bryan

Re: [yocto] update mechanisms

On 12/12/16 09:41, Patrick Ohly wrote: > On Mon, 2016-12-12 at 08:59 -0600, Mariano Lopez wrote: In particular the "complexity" column is a bit subjective. Stefano, I hope you don't mind that I did not quite buy the "easy to use" characterization of swupdate ;-) >>> No worry...and

Re: [yocto] suggestions for version controlling multi-layer reproducible builds?

Robert, > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Robert P. J. Day > Sent: Monday, December 12, 2016 10:20 AM > To: Yocto discussion list > Subject: [yocto] suggestions for version

[yocto] Yocto Project Status WW51

Current Dev Position: YP 2.3 M1 -> M2 Next Deadline: YP 2.3 M1 by Dec. 12, 2016 (TODAY!!) YP 2.3 M2 by Jan 23, 2017 SWAT team rotation: Tracy -> Alejandro https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: * Today is the M1 feature

Re: [yocto] update mechanisms

On Mon, 2016-12-12 at 08:59 -0600, Mariano Lopez wrote: > >> In particular the "complexity" column is a bit subjective. Stefano, I > >> hope you don't mind that I did not quite buy the "easy to use" > >> characterization of swupdate ;-) > > No worry...and I have not written myself. It was inserted

Re: [yocto] update mechanisms

On Mon, 2016-12-12 at 15:13 +, André Draszik wrote: > Hi, > > On Tue, 2016-12-06 at 10:45 +0100, Patrick Ohly wrote: > > I'll do the same for swupd. Editing the sections should be possible > > without conflicts, we just have to be more careful about editing the > > table concurrently. > >

Re: [yocto] suggestions for version controlling multi-layer reproducible builds?

Hi, On 12/12/2016 05:03 PM, Bryan Evenson wrote: > > For my setup I have a separate package that is the distribution > version number. Whenever we release an update, the distribution > version number is updated. We then tag all our layers with the > distribution version number for proper

Re: [yocto] update mechanisms

On Mon, 2016-12-12 at 09:49 -0600, Mariano Lopez wrote: > > On 12/12/16 09:41, Patrick Ohly wrote: > > On Mon, 2016-12-12 at 08:59 -0600, Mariano Lopez wrote: > In particular the "complexity" column is a bit subjective. Stefano, I > hope you don't mind that I did not quite buy the "easy

Re: [yocto] Can't enable reverse debugging

Khem, > -Original Message- > From: Khem Raj [mailto:raj.k...@gmail.com] > Sent: Monday, December 12, 2016 12:48 PM > To: Bryan Evenson > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Can't enable reverse debugging > > > > On Dec 12, 2016, at 6:59 AM, Bryan

Re: [yocto] Can't enable reverse debugging

> On Dec 12, 2016, at 6:59 AM, Bryan Evenson wrote: > > Khem, > >> -Original Message- >> From: Khem Raj [mailto:raj.k...@gmail.com] >> Sent: Saturday, December 10, 2016 4:26 PM >> To: Bryan Evenson >> Cc: yocto@yoctoproject.org >>

Re: [yocto] Can't enable reverse debugging

> On Dec 12, 2016, at 11:12 AM, Bryan Evenson wrote: > > Khem, > >> -Original Message- >> From: Khem Raj [mailto:raj.k...@gmail.com] >> Sent: Monday, December 12, 2016 12:48 PM >> To: Bryan Evenson >> Cc: yocto@yoctoproject.org >>

[linux-yocto] [PATCH 2/5] iio: adc: ti-ads1015: add support for ADS1115 part

From: Matt Ranostay Backported from linux-yocto-4.8: ba35f111aa6f386df33f950aeaea53a2bf040cc2 TI ADS1115 is a 16-bit resolution ADC that is register map compatible with the ADS1015 device. Signed-off-by: Matt Ranostay Acked-by: Daniel Baluta

[linux-yocto] [PATCH 1/5] iio: adc: Add TI ADS1015 ADC driver support

From: Daniel Baluta Backported from linux-yocto-4.8: ecc24e72f43735cceab06f4e69aa6ce075a3ae46 The driver has sysfs readings with runtime PM support for power saving. It also offers buffer support that can be used together with IIO software triggers. Datasheet can be

[linux-yocto] [PATCH 0/5] Backport from 4.8: iio: ti-ads1015 support

From: Tuomas Katila Patches are intended for the bxt-rebase branch Backported ti-ads1015 support from linux-yocto 4.8 kernel. The chip is supported in some Joule extender boards, such as Gravity Expansion Shield for Intel Joule SKU: DFR0465. Also added ACPI support for

[linux-yocto] [PATCH 5/5] iio: adc: ti-ads1015: add support for acpi

From: Tuomas Katila Add support for acpi platform configuration. Signed-off-by: Tuomas Katila --- drivers/iio/adc/ti-ads1015.c | 34 +- 1 file changed, 33 insertions(+), 1 deletion(-) diff --git

[linux-yocto] [PATCH 3/5] iio: adc: ti-ads1015: add datasheet names

From: Matt Ranostay Backported from linux-yocto-4.8: 8ac8aa61f87eda944cf29229c9c20cba9e83f1ea Add datasheet names for ADC channels to allow iio consumers access. Signed-off-by: Matt Ranostay Acked-by: Daniel Baluta

[linux-yocto] [PATCH 4/5] iio: adc: ti-ads1015: add indio_dev->dev.of_node reference

From: Matt Ranostay Backported from linux-yocto-4.8: f5241dbdfef4404b4e80f0bda13e5c7ceba3ee4a Add the pointer to the device tree node of the ADC so that iio consumers can reference the respective channels. Signed-off-by: Matt Ranostay Acked-by: Daniel

[linux-yocto] [yocto-kernel-cache][PATCH] netfilter: enable connection tracking for IPv6

In case of the DROP policy in the INPUT chain a host using IPv6 still might need to receive TCP packets for established connections, that is to have the rule -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT in its INPUT chain of ip6tables. For this feature to work the option