Re: [yocto] BBMASK not working for me?

On Wed, Mar 1, 2017 at 5:39 PM, Paul Eggleton wrote: > On Thursday, 2 March 2017 2:14:13 PM NZDT chris warth wrote: > > wrote: > > > On Thursday, 2 March 2017 11:31:42 AM NZDT chris warth wrote: > > >> This vendor-supplied version

Re: [yocto] BBMASK not working for me?

On Thursday, 2 March 2017 2:14:13 PM NZDT chris warth wrote: > wrote: > > On Thursday, 2 March 2017 11:31:42 AM NZDT chris warth wrote: > >> This vendor-supplied version of yocto looks like 2.0, so the space > >> separated expressions are not available. > >> After

Re: [yocto] BBMASK not working for me?

Thank you, Paul. I didn't know about bitbake -e. As you predicted, it shows that an earlier layer is setting BBMASK with equals, in this case the meta-freescale layer. BBMASK=".*openjre|.*openjdk" Should I be mad at the vendor for being careless? Is BBMASK_forcevariable the right workaround for

Re: [yocto] BBMASK not working for me?

Hi Chris, On Thursday, 2 March 2017 11:31:42 AM NZDT chris warth wrote: > Thanks, all. I wanted to share the solution. > > This vendor-supplied version of yocto looks like 2.0, so the space > separated expressions are not available. > After putting some print statements in cooker.py I

Re: [yocto] update mechanisms

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 > > moment, but might

Re: [yocto] BBMASK not working for me?

Thanks, all. I wanted to share the solution. This vendor-supplied version of yocto looks like 2.0, so the space separated expressions are not available. After putting some print statements in cooker.py I discovered that appending to BBMASK in conf/bblayers.conf or conf/local.conf has no effect.

Re: [yocto] BBMASK not working for me?

On Wed, Mar 1, 2017 at 12:15 PM, Jeremy A. Puhlman wrote: > > On 3/1/2017 12:06 PM, chris warth wrote: > > Can anyone suggest why my BBMASK is not working? > Maybe I'm not putting it into the right file? > Did I construct the regex incorrectly? > > In my conf/bblayers.conf I

Re: [yocto] BBMASK not working for me?

On 3/1/2017 12:06 PM, chris warth wrote: Can anyone suggest why my BBMASK is not working? Maybe I'm not putting it into the right file? Did I construct the regex incorrectly? In my conf/bblayers.conf I have, BBMASK .= "qemu" This basically concatenates qemu to what ever is already in

[yocto] BBMASK not working for me?

Can anyone suggest why my BBMASK is not working? Maybe I'm not putting it into the right file? Did I construct the regex incorrectly? In my conf/bblayers.conf I have, BBMASK .= "qemu" Then I wipe out the cache by deleting the "tmp/" directory. Now I would expect bitbake -n -c fetch

[yocto] Yocto create tar image Permissions error, tar: ./etc/gshadow+: Cannot open: Permission denied

Hello, I am using Yocto Project Krogoth 2.1.2. And sometimes it happens to me that in the final stage create tar image do_package it will fire error bellow about wrong permissions. tar: ./etc/gshadow+: Cannot open: Permission denied It happens when tar is doing archive. I am doing always clean

Re: [yocto] [OE-core] [PATCHv2] yocto-compat-layer.py: Add script to YP Compatible Layer validation

On Wed, 2017-03-01 at 16:01 +, Richard Purdie wrote: > On Wed, 2017-03-01 at 16:51 +0100, Patrick Ohly wrote: > > On Wed, 2017-03-01 at 15:12 +, Richard Purdie wrote: > > > > > > On Wed, 2017-03-01 at 08:10 +0100, Patrick Ohly wrote: > > > > > > > > Is the "build single distro for

[yocto] how to use yocto make Individual components

i have got an image with yocto & bitbake,now, i want to figure out what happend with the u-boot and kernel when i run the command "bitbake target",how does these task modify the source code of u-boot and kernel. thank you! -- ___ yocto mailing list

Re: [yocto] [OE-core] [PATCHv2] yocto-compat-layer.py: Add script to YP Compatible Layer validation

On Wed, 2017-03-01 at 16:51 +0100, Patrick Ohly wrote: > On Wed, 2017-03-01 at 15:12 +, Richard Purdie wrote: > > > > On Wed, 2017-03-01 at 08:10 +0100, Patrick Ohly wrote: > > > > > > Is the "build single distro for different machines" scenario that > > > I > > > described part of the Yocto

Re: [yocto] [OE-core] [PATCHv2] yocto-compat-layer.py: Add script to YP Compatible Layer validation

On Wed, 2017-03-01 at 15:12 +, Richard Purdie wrote: > On Wed, 2017-03-01 at 08:10 +0100, Patrick Ohly wrote: > > Is the "build single distro for different machines" scenario that I > > described part of the Yocto Compliance 2.0? Should there be tests for > > it? > > Right now its not Okay,

Re: [yocto] [OE-core] [PATCHv2] yocto-compat-layer.py: Add script to YP Compatible Layer validation

On Wed, 2017-03-01 at 08:10 +0100, Patrick Ohly wrote: > On Wed, 2017-03-01 at 04:00 +, Richard Purdie wrote: > > > > On Tue, 2017-02-28 at 21:09 +0100, Patrick Ohly wrote: > > > > > > On Mon, 2017-02-20 at 15:12 -0600, Aníbal Limón wrote: > > > > > > > > > > > > common.test_signatures:

Re: [linux-yocto] [meta-intel] update kernel in local.conf

Hi, I accidentally ran into this too and looked into it a bit. There are two kernels in the package feedwhich Provides:the same functionality. The one that's built afterwards is tracked in pkgdata as runtime-reverse but the package manager has installed the other (returned by

Re: [yocto] error while compiling external module in Krogoth branch

Hi, Already patched is applied in latest Yocto source. Thanks, Praveen. On Tue, Feb 28, 2017 at 8:31 PM, Khem Raj wrote: > > On Tue, Feb 28, 2017 at 5:27 AM praveen vattipalli > wrote: > >> Hi, >> I am using krogoth branch of meta-altera. >> in

[yocto] Using armcc in Yocto

Hello, I have an application which I am building for Yocto using the POKY toolchain (arm-poky-linux-gnueabi) and running on a BeagleBoneBlack device. Is it possible to compile using the ARM compiler (armcc, armlink) and still target the linux-yocto OS? Is it something that was done before?

[yocto] [meta-rockchip][PATCH 2/2] recipes-graphics: Add recipe for libdrm-rk

It's rockchip modified libdrm, we can call rga by this libdrm. Our development work in libdrm has not yet completed, so it have not pushed to the upstream. We temporarily maintain it by ourself. --- recipes-graphics/libdrm/libdrm_rk.bb | 47 1 file changed,

[yocto] [meta-rockchip][PATCH 1/2] udev-extraconf: add rockchip specific rules

This rules file help to set suitable mode for device node. vpu-service, vpu_service, rkvdec, hevc-service are different ip. mali0 is mali-midgard and mali is mali-utgard. Signed-off-by: Jacob Chen --- recipes-core/udev/udev-extraconf/10-rk.rules | 6 ++

Re: [yocto] [PATCH] recipes-graphics: Add recipe for libdrm-rk

oh， i forget to add meta-rockchip too. 2017-03-01 18:30 GMT+08:00 Jacob Chen : > It's rockchip modified libdrm, we can call rga by this libdrm. > > Our development work in libdrm has not yet completed, so it have not pushed > to the upstream. > We temporarily maintain it

Re: [yocto] [PATCH] udev-extraconf: add rockchip specific rules

oh， i forget to add meta-rockchip too. 2017-03-01 18:23 GMT+08:00 Jacob Chen : > This rules file help to set suitable mode for device node. > > vpu-service, vpu_service, rkvdec, hevc-service are different ip. > mali0 is mali-midgard and mali is mali-utgard. > >

[yocto] [PATCH] recipes-graphics: Add recipe for libdrm-rk

It's rockchip modified libdrm, we can call rga by this libdrm. Our development work in libdrm has not yet completed, so it have not pushed to the upstream. We temporarily maintain it by ourself. --- recipes-graphics/libdrm/libdrm_rk.bb | 47 1 file changed,

[yocto] [PATCH] udev-extraconf: add rockchip specific rules

This rules file help to set suitable mode for device node. vpu-service, vpu_service, rkvdec, hevc-service are different ip. mali0 is mali-midgard and mali is mali-utgard. Signed-off-by: Jacob Chen --- recipes-core/udev/udev-extraconf/10-rk.rules | 6 ++