Re: [yocto] NXP Yocto imx-linux-sumo can't boot

Hi, Assuming you have a tar ball of the image the steps are roughly: 1. Format storage device (USB stick or SD card) in expected format, e.g. ext4 2. Mount storage device 3. Expand the rootfs onto the storage device, e.g. from the USB root directory: sudo tar --numeric-owner --preserve-permission

Re: [yocto] [Openembedded-architecture] Dropping armv5 and armv5e tunes in 2.7

Thanks Adrian On Thu, Jan 3, 2019 at 2:59 PM Adrian Bunk wrote: > > On Thu, Jan 03, 2019 at 02:01:42PM -0800, Khem Raj wrote: > > Hello All > > > > You might have noticed a recent commit in gcc trunk > > > > https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=b232e6b58e3766bc66fe08fdb7bcba1bdadda8a2 >

Re: [yocto] [Openembedded-architecture] Dropping armv5 and armv5e tunes in 2.7

On Thu, Jan 03, 2019 at 02:01:42PM -0800, Khem Raj wrote: > Hello All > > You might have noticed a recent commit in gcc trunk > > https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=b232e6b58e3766bc66fe08fdb7bcba1bdadda8a2 > > Which removed support for deprecated -march=armv5 and armv5e, this > will b

Re: [yocto] [meta-security][PATCH] checksec: Upgrade to 1.11.0

On 1/3/19 9:02 AM, Scott Ellis wrote: > Switch source to a more up to date github repo. Very cool. > > Signed-off-by: Scott Ellis > --- > recipes-security/checksec/checksec_1.11.bb | 19 +++ > 1 file changed, 19 insertions(+) > create mode 100644 recipes-security/checksec/chec

[yocto] Dropping armv5 and armv5e tunes in 2.7

Hello All You might have noticed a recent commit in gcc trunk https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=b232e6b58e3766bc66fe08fdb7bcba1bdadda8a2 Which removed support for deprecated -march=armv5 and armv5e, this will be released along with gcc-9 release which is upcoming and we might be able

Re: [yocto] [PATCH][ptest-runner] ptest-runner: Add support timeout failure type to XML result file

On Thu, 2019-01-03 at 12:02 -0600, Aníbal Limón wrote: > The ptest-runner support logging results to stdout and to a XML file > in stdout the ptest is mark as: > > ... > ERROR: Exit status is 1 > TIMEOUT: ptest-directory > ... > > Add the same support in XML file for example, > > ... > > >

Re: [yocto] Python upgrade path?

Yep, that’s all reasonable. Devtool won’t help you with rebasing patches to poky tree. It has a facility for upgrading recipes, but it’s likely to fail in non trivial ways for something as complex as python. You’re better off taking existing patches and getting them to work I’d say. Alex > On

[yocto] [PATCH][ptest-runner] ptest-runner: Add support timeout failure type to XML result file

The ptest-runner support logging results to stdout and to a XML file in stdout the ptest is mark as: ... ERROR: Exit status is 1 TIMEOUT: ptest-directory ... Add the same support in XML file for example, ... ... [YOCTO #13088] Signed-off-by: Aníbal Limón --- tests/data/reference.xml

[yocto] [meta-security][PATCH] checksec: Upgrade to 1.11.0

Switch source to a more up to date github repo. Signed-off-by: Scott Ellis --- recipes-security/checksec/checksec_1.11.bb | 19 +++ 1 file changed, 19 insertions(+) create mode 100644 recipes-security/checksec/checksec_1.11.bb diff --git a/recipes-security/checksec/checksec_1.1

Re: [yocto] How to skip a receipe from security_flags by its name?

Have a look at security_flags.inc, you'll see that the bulk of it is exactly this per-recipe exclusion. Ross On Fri, 28 Dec 2018 at 17:19, Stefano Cappa wrote: > > Hi! > > Let say that I have a receipe called "third-party-receipe" and I want to use > security flags for everything except for "th

Re: [yocto] Python upgrade path?

On Thu, 3 Jan 2019 at 10:11, Derek Dresser wrote: > I have an application that uses features introduced in Python 3.6, so I am > trying to add a new version of Python to my Yocto build. I know that 3.5.6 > is the latest version of Python that has been included in a Yocto release. I > found th

Re: [yocto] devtool to built for update repo revision

On Thu, 3 Jan 2019 at 10:09, Peter Balazovic wrote: > I am trying to use "devtool" from eSDK to create own recipe. At first it > works with repo and can generate recipe and binaries and deploy to target > machine. > > Now I'd like to update it with a new revision of source code. > So I updated S

Re: [yocto] devtool upgrade ERROR: recipe is already in your workspace

On Thu, 3 Jan 2019 at 10:10, Peter Balazovic wrote: > I have created recipe with devtool and now I want to upgrade following > > > devtool upgrade myrecipe --srcrev 82a02d8585d262d6ab2d9dc335ed2231dc2d7f06 > > I am getting error > > > ERROR: recipe is already in your workspace > > How to correctly

[yocto] The Yocto compatible of 'meta' layer with script/yocto-check-layer

hello, I am not sure whether this email list is right list to discuss the question about the Yocto compatible of 'meta' layer when checking with 'script/yocto-check-layer', the error message like below: ERROR: meta: Can't be DISTRO and BSP type at the same time. The conf/distro and conf/machi

Re: [yocto] Accelerate kernel module built in eSDK?

On 2018/12/28 23:01, richard.pur...@linuxfoundation.org wrote: On Fri, 2018-12-28 at 22:35 +0800, Zhaolong Zhang wrote: On 2018/12/28 19:40, richard.pur...@linuxfoundation.org wrote: On Fri, 2018-12-28 at 18:19 +0800, Zhaolong Zhang wrote: Hi Experts, Building out-of-tree kernel modules in eS

Re: [yocto] Accelerate kernel module built in eSDK?

On 2018/12/28 22:35, Zhaolong Zhang wrote: On 2018/12/28 19:40, richard.pur...@linuxfoundation.org wrote: On Fri, 2018-12-28 at 18:19 +0800, Zhaolong Zhang wrote: Hi Experts, Building out-of-tree kernel modules in eSDK will trigger a new rebuilding of kernel, which consumes lots of time. Is it

[yocto] Accelerate kernel module built in eSDK?

Hi Experts, Building out-of-tree kernel modules in eSDK will trigger a new rebuilding of kernel, which consumes lots of time. Is it possible to cache the do_shared_workdir() task in sstate-cache and ship it within eSDK? And how? Or is there other method to accelerate? Thanks in advance. Reg

Re: [yocto] Accelerate kernel module built in eSDK?

On 2018/12/28 19:40, richard.pur...@linuxfoundation.org wrote: On Fri, 2018-12-28 at 18:19 +0800, Zhaolong Zhang wrote: Hi Experts, Building out-of-tree kernel modules in eSDK will trigger a new rebuilding of kernel, which consumes lots of time. Is it possible to cache the do_shared_workdir() t

Re: [yocto] Yocto staged builds?

> -Original Message- > From: Burton, Ross > Sent: Tuesday, December 18, 2018 12:48 PM > To: Edmund Nadolski > Cc: Yocto-mailing-list > Subject: Re: [yocto] Yocto staged builds? > > On Tue, 18 Dec 2018 at 16:07, Edmund Nadolski > wrote: > > Create and sign binary files (ie kernel, modul

[yocto] Python upgrade path?

Hello, I have an application that uses features introduced in Python 3.6, so I am trying to add a new version of Python to my Yocto build. I know that 3.5.6 is the latest version of Python that has been included in a Yocto release. I found the patches here https://patchwork.openembedded.org/series

Re: [yocto] Yocto usability questions

I am getting permission denied error when trying to build in yacto build environment.source code repository for Uboot I have kept in gitlab.com and other build related dependencies I have kept in github.com. I have downloaded(git clone) the built platform in my local machine. I made changes in sour

[yocto] devtool upgrade ERROR: recipe is already in your workspace

I have created recipe with devtool and now I want to upgrade following > devtool upgrade myrecipe --srcrev 82a02d8585d262d6ab2d9dc335ed2231dc2d7f06 I am getting error > ERROR: recipe is already in your workspace How to correctly upgrade recipe with devtool (eSDK)? -- __

[yocto] devtool to built for update repo revision

Hello, I am trying to use "devtool" from eSDK to create own recipe. At first it works with repo and can generate recipe and binaries and deploy to target machine. Now I'd like to update it with a new revision of source code. So I updated SRCREV per released commit and as well add *PV = "0.1+git${

[yocto] NXP Yocto imx-linux-sumo can't boot

After building an image out of repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-sumo -m imx-4.14.78-1.0.0_ga.xml build on 8qm machine MACHIN