Re: [yocto] [meta-raspberrypi][PATCH v4 0/5] Support for .dtbo files for dtb overlays, required by kernels 4.4.6+

Hi Andrei, I believe it still has not been merged... Shall I send a ping? Herve -Original Message- From: Andrei Gherzan [mailto:and...@gherzan.ro] Sent: mercredi 15 juin 2016 01:54 To: Herve Jourdain Cc: yocto@yoctoproject.org Subject: Re: [yocto]

Re: [linux-yocto] [PULL REQUEST] Watchdog parenting fix for linux-yocto-4.1

On 2016-06-13 9:59 PM, Yong, Jonathan wrote: This series of 11 patches from Linus's tree fixes the parenting of watchdog devices. To do that, a lot of OMAP watchdog fixes are pulled in as dependencies. I've grabbed the changes. After my sanity tests pass, I'll send SRCREV updates. Bruce

Re: [linux-yocto] [PULL REQUEST] Watchdog parenting fix for linux-yocto-4.1

On 2016-06-14 2:28 AM, Yong, Jonathan wrote: On 06/14/2016 09:59, Yong, Jonathan wrote: This series of 11 patches from Linus's tree fixes the parenting of watchdog devices. To do that, a lot of OMAP watchdog fixes are pulled in as dependencies. Adds Conexant Digicolor CX9 and

Re: [linux-yocto] [PATCH 0/2] Backport pinctrl/intel patches from mainline kernel into linux-yocto-4.1

On 2016-06-14 1:44 AM, Tan Jui Nee wrote: Hi Bruce, The patches are to backport Intel Broxton / Apollo Lake patches that are available in the mainline Linux kernel, upstreamed by Qipeng Zha. The patches are to fix GPIO register offset calculation for Intel Broxton / Apollo Lake. The patches

Re: [linux-yocto] [PATCH 0/8] TPM 2.0 support for linux-yocto-4.1

On 2016-06-14 12:14 AM, jonathan.y...@intel.com wrote: From: "Yong, Jonathan" These patches introduces TPM 2.0 support, and are backported from Linus's tree. Should apply cleanly for linux-yocto-4.1 stadard/base. They do apply cleanly. I've staged them in my tree,

Re: [linux-yocto] [PATCH] MAINTAINER file update for TPM 2.0 series

On 2016-06-14 12:18 AM, jonathan.y...@intel.com wrote: From: "Yong, Jonathan" Oops, missed this commit, this should be part of the TPM 2.0 series. For linux-yocto-4.1 standard/base. No worries. I've added it to the queue. Bruce Jarkko Sakkinen (1): MAINTAINERS:

Re: [linux-yocto] [PATCH] powercap/RAPL: disable the 2nd power limit properly

On 2016-06-13 8:29 AM, ong.hock...@intel.com wrote: From: "Yu, Ong Hock" This patch back port the upstream patch to properly handle the 2nd RAPL limit. This patch is intended for kernel 4.1. I've staged the patch. Once my sanity builds have passed, I'll send SRCREV

Re: [yocto] [meta-raspberrypi][PATCH 1/6] linux-raspberrypi: Allow override of PV

On Fri, Jun 03, 2016 at 08:47:45PM +0100, Paul Barker wrote: > On Fri, 3 Jun 2016 09:07:37 +0300 > Ionel Badisor wrote: > > > On 06/03/2016 12:25 AM, Paul Barker wrote: > > > On Thu, 2 Jun 2016 10:59:37 +0300 > > > Ionel Badisor wrote: > > > > > >>

Re: [yocto] [meta-raspberrypi][PATCH 1/6] linux-raspberrypi: Allow override of PV

On Sun, May 29, 2016 at 04:59:08PM +0100, Paul Barker wrote: > PV is now set in each version of the linux-raspberrypi recipe instead of in > linux-raspberrypi.inc. This allows linux-raspberrypi.inc to be used in custom > kernel recipes in another layer which require a different PV value. > >

Re: [yocto] [meta-raspberrypi][PATCH v4 3/5] rpi-base.inc: support for .dtbo files for dtb overlays

On Tue, May 31, 2016 at 04:46:33AM +0800, Herve Jourdain wrote: > Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of > .dtb. > Add support for both variants of overlays ("-overlay.dtb" and ".dtbo") for > the default KERNEL_DEVICETREE variable > > Signed-off-by: Herve

Re: [yocto] [meta-raspberrypi][PATCH v4 4/5] linux-raspberrypi_4.4.inc: support for .dtbo files for dtb overlays

On Tue, May 31, 2016 at 04:46:34AM +0800, Herve Jourdain wrote: > Kernel 4.4.6+ on RaspberryPi support .dtbo files for overlays, instead of > .dtb. > Patch the kernel, which has faulty rules to generate .dtbo the way yocto does > You need an Upstream status here:

Re: [yocto] [meta-raspberrypi][PATCH v4 5/5] linux-raspberrypi_4.4.inc: support for .dtbo files for dtb overlays

On Tue, May 31, 2016 at 04:46:35AM +0800, Herve Jourdain wrote: > Signed-off-by: Herve Jourdain > --- > recipes-kernel/linux/linux-raspberrypi_4.4.bb | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb >

Re: [yocto] [meta-raspberrypi][PATCH v4 0/5] Support for .dtbo files for dtb overlays, required by kernels 4.4.6+

On Tue, May 31, 2016 at 04:46:30AM +0800, Herve Jourdain wrote: > v4: rebased > For kernels 4.4.9+, the behavior for the device tree overlays loading has > been modified on RaspberryPi. > For overlays, it loads .dtbo files, not .dtb anymore. > Also, it does not check for -overlay extension, so

Re: [yocto] [meta-raspberrypi][PATCH 1/1] linux-raspberrypi.inc: KERNEL_OUTPUT has been removed in kernel.bbclass

Hi, On Tue, May 31, 2016 at 07:58:59PM +0800, Herve Jourdain wrote: > Signed-off-by: Herve Jourdain > --- > recipes-kernel/linux/linux-raspberrypi.inc | 8 ++-- > 1 file changed, 6 insertions(+), 2 deletions(-) > > diff --git

[yocto] [PATCH 2/2] linux-raspberrypi: Fix v4.1 with GCC6

Signed-off-by: Andrei Gherzan --- ...ove-unused-sm_cache_map_vector-definition.patch | 31 + .../linux-raspberrypi-4.1/0003-fix-gcc6.patch | 78 ++ recipes-kernel/linux/linux-raspberrypi_4.1.bb | 2 + 3 files changed, 111 insertions(+)

[yocto] [PATCH 1/2] packagegroup-rpi-test: Poky moved the license so fix LIC_FILES_CHKSUM

Signed-off-by: Andrei Gherzan --- recipes-core/packagegroups/packagegroup-rpi-test.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-core/packagegroups/packagegroup-rpi-test.bb b/recipes-core/packagegroups/packagegroup-rpi-test.bb index

Re: [yocto] Customization for nginx

Hi Virgil On 2016-06-14, Smith, Virgil wrote: "How do you prefer a provider out of two different versions of a package?" PREFERRED_VERSION http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#var-PREFERRED_VERSION Thanks. Worked fine. -- Greetings Elias --

Re: [yocto] [[PATCH][error-report-web] 5/8] Post/models.py: Build model add support for Error type.

On 06/14/2016 11:44 AM, Aníbal Limón wrote: > > > On 06/14/2016 08:30 AM, Michael Wood wrote: >> On 14/06/16 00:32, Aníbal Limón wrote: >>> In order to support other errors not only Recipe ones adds >>> a ERROR_TYPE field to the Build model defaults to "Recipe". >>> >>> Add a class for store

Re: [yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi: Prevent taskhash mismatch

Hi Paul, On Wed, Jun 08, 2016 at 02:02:29PM +0100, Paul Barker wrote: > As recently discussed on the mailing list, bitbake now issues an error when > the > task hash computed by the bitbake master differs from the task hash computed > by > the bitbake worker. This usually happens when the task

Re: [yocto] Customization for nginx

"How do you prefer a provider out of two different versions of a package?" PREFERRED_VERSION http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#var-PREFERRED_VERSION Notice to recipient: This email is meant for only the intended recipient of the

Re: [yocto] Customization for nginx

Hi Piotr On 2016-06-14, piotr.lewicki wrote: This is not an answer to your question but it can be helpful: You can use a wildcard for version in your bbappend file. If you rename it to: nginx_1.9.%.bbappend this will work for both 1.9.5 and 1.9.14. Thanks for this hint. I realized that

Re: [yocto] [yocto-autobuilder] [RFC] Add support for generate bitbake error reports

On 06/14/2016 10:57 AM, Aníbal Limón wrote: > > > On 06/14/2016 10:09 AM, Lock, Joshua G wrote: >> On Thu, 2016-06-09 at 16:23 -0500, Aníbal Limón wrote: >>> Hi folks, >>> >>> Currently we support to send error reports to errors.yoctoproject.org >>> about failing tasks on bitbake using

Re: [yocto] [meta-raspberrypi][PATCH] omxplayer: fix compilation with GCC 6

Hi, On Wed, Jun 08, 2016 at 12:57:13AM +1000, Jonathan Liu wrote: > Specifying -isystem${STAGING_DIR_HOST}/usr/include in INCLUDES gives: > > In file included from utils/PCMRemap.cpp:26:0: > .../build/tmp/sysroots/raspberrypi2/usr/include/c++/6.1.1/cstdlib:75:25: > fatal error: stdlib.h:

Re: [yocto] [[PATCH][error-report-web] 5/8] Post/models.py: Build model add support for Error type.

On 06/14/2016 08:30 AM, Michael Wood wrote: > On 14/06/16 00:32, Aníbal Limón wrote: >> In order to support other errors not only Recipe ones adds >> a ERROR_TYPE field to the Build model defaults to "Recipe". >> >> Add a class for store BuildErrorType currently supported >> Recipe, Core,

Re: [yocto] Script being installed under /etc/init.d instead of /usr/lib/systemd folder

On 9 June 2016 at 02:11, Dey, Megha wrote: > However, I do have a script recipe which is currently placed as a bbappend > to initscripts (meta/recipes-core/initscripts/initscript_..bb) in my custom > meta layer. > > > > This script even after shifting to systemd, is being

Re: [yocto] Mounting USB drives on a "read-only-rootfs" based system

There's also bind mounts as an option. The bind mounts. Since Linux 2.4.0 it is possible to remount part of the file hierarchy somewhere else. The call is: mount --bind olddir newdir or by using this fstab entry:

Re: [yocto] [yocto-autobuilder] [RFC] Add support for generate bitbake error reports

On 06/14/2016 10:09 AM, Lock, Joshua G wrote: > On Thu, 2016-06-09 at 16:23 -0500, Aníbal Limón wrote: >> Hi folks, >> >> Currently we support to send error reports to errors.yoctoproject.org >> about failing tasks on bitbake using SendErrorReport buildstep but we >> have a lack of bitbake

Re: [yocto] Script being installed under /etc/init.d instead of /usr/lib/systemd folder

Take a look at example from my some-recipe.bb : inherit systemd SYSTEMD_SERVICE_${PN} = "some-recipe.service" do_install_append () { install -d ${D}${systemd_unitdir}/system install -m 0644 ${S}/configs/some-recipe.service ${D}${systemd_unitdir}/system } First in your recipe inherit

Re: [yocto] [yocto-autobuilder] [RFC] Add support for generate bitbake error reports

(Resent including the list, apologies for those receiving it again) On Thu, 2016-06-09 at 16:23 -0500, Aníbal Limón wrote: > Hi folks, > > Currently we support to send error reports to errors.yoctoproject.org > about failing tasks on bitbake using SendErrorReport buildstep but we > have a lack

Re: [yocto] resolvconf nameserver

Yes, I tried that already. Thanks, Monica From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Monday, June 13, 2016 4:58 PM To: Rajasekaran, Monica Cc: yocto@yoctoproject.org Subject: Re: [yocto] resolvconf nameserver On 13 June 2016 at 22:47,

Re: [yocto] Mounting USB drives on a "read-only-rootfs" based system

On 14 June 2016 at 14:48, Jeffrey D Boyer wrote: > FYI, I'm running 3.14 kernel. Is this a job for aufs? If so, how would I > go about configuring it? > If you want to support arbitrary mounts then it's probably simplest to either change /media to be a symlink to

Re: [yocto] Mounting USB drives on a "read-only-rootfs" based system

Sorry, /media is not a symlink and there is no /run/media link or directory present on my running system. When I insert an SD card, for example, I get a bit of text on the debug serial port that a card has been detected, but I don't see a mount point anywhere after that. root@mySys:/#

Re: [yocto] [[PATCH][error-report-web] 5/8] Post/models.py: Build model add support for Error type.

On 14/06/16 00:32, Aníbal Limón wrote: In order to support other errors not only Recipe ones adds a ERROR_TYPE field to the Build model defaults to "Recipe". Add a class for store BuildErrorType currently supported Recipe, Core, Bitbake selftest and OE selftest. [YOCTO #7583] Signed-off-by:

Re: [yocto] Mounting USB drives on a "read-only-rootfs" based system

Yup, even mdev based images do that with current OE. I'd expect "/media" to symlink to "run/media" on most devices (regardless whether the rootfs is read-only or not). Check if that's the case on your system. On 14-06-16 00:01, Christopher Larson wrote: Afaik usb storage is already

[yocto] Test Cycle Report for Yocto Project master branch

Hi Here is the status for the test cycle of automated tests on master branch commit 6c5d7f1fb276cbe0a461ece6c8f0ca17a478fa8c Summary : - Toaster - NameError when trying to search a table due Django, this one is blocking around 30% of the execution : 9749 [1] - Build

Re: [yocto] Customization for nginx

This is not an answer to your question but it can be helpful: You can use a wildcard for version in your bbappend file. If you rename it to: nginx_1.9.%.bbappend this will work for both 1.9.5 and 1.9.14. For debugging I can give you a hint: try using "-v" switch for bitbake when baking your

[yocto] [Found Error] Re: License problems when switching form RPM to DEB - looking for a easy way to fix it

Hej I found the error at the QA check of the debian packages. The deb QA modul has problems resolving the links into the "sysroots//pkgdata/runtime-resolve". This is because there is a lowcase conversation of the recipe name: p.e.: "helloMyWorld.bb" the name of the link is "helloMyWorld"

[yocto] Customization for nginx

Hi With jethro, I used to use the following .bbappend to use my config for nginx: FILESEXTRAPATHS_prepend := "${THISDIR}/files:" My nginx.conf was inside the corresponding files directory. Since krogoth, which uses nginx 1.9.14, this does not seem to work any more. My config file is not

Re: [yocto] Mounting USB drives on a "read-only-rootfs" based system

Hi, you can adjust the mount behaviour for example in your udev mount script (if you use udev). If you have a fixed name/mountpoint for your media you can pre-create that folder (for example /media/data-logging) and let udev's mount.sh mount media which matches your criteria to that path. kind

Re: [linux-yocto] [PULL REQUEST] Watchdog parenting fix for linux-yocto-4.1

On 06/14/2016 09:59, Yong, Jonathan wrote: This series of 11 patches from Linus's tree fixes the parenting of watchdog devices. To do that, a lot of OMAP watchdog fixes are pulled in as dependencies. Adds Conexant Digicolor CX9 and STMicroelectronics LPC Watchdog.