Re: [yocto] Error in building new recipe for Jool network translator

Thanks Mark, I'll check them out. Regards, Gokul Raj K On Fri, 7 Jun, 2019, 2:54 AM Mark Hatle, wrote: > On 6/6/19 11:46 AM, Gokul Raj wrote: > > Hi Ross, > > > > Thanks for the suggestion. I have tried with inheriting > autotools-brokensep > > bbclass. Now bitbake got the path for

Re: [yocto] [PATCH][yocto-docs] ref-manual: Corrected openSUSE essential packages

On 6/6/19 4:46 PM, Michael Halstead wrote: > Some packages were bumped onto the pip3 install line. Install them with > zypper as before. with backport? ie is Warrior or Thud affected, I suspect so - armin > > Signed-off-by: Michael Halstead > --- > documentation/poky.ent | 4 ++-- > 1 file

Re: [yocto] Error in building new recipe for Jool network translator

On Thu, 2019-06-06 at 22:16 +0530, Gokul Raj wrote: > Hi Ross, > > Thanks for the suggestion. I have tried with inheriting autotools- > brokensep bbclass. Now bitbake got the path for compilation. But, > bitbake compilation refering to native kernel src path for module > compilation. For your

Re: [yocto] arm yocto-linux custom defconfig not working

On Thu, Jun 6, 2019 at 10:06 AM Pierluigi Greto wrote: > > Hi, > > thank you for the reply. In the attahcment the layer for the kernel and > the layer with the machine configurations. Thanks for the layers. I was able to pull together a thud build env and do some tests. For me, I see the

[yocto] [PATCH][yocto-docs] ref-manual: Corrected openSUSE essential packages

Some packages were bumped onto the pip3 install line. Install them with zypper as before. Signed-off-by: Michael Halstead --- documentation/poky.ent | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/poky.ent b/documentation/poky.ent index

Re: [yocto] Support NAND flash

Thanks Josef for the response and links, the board is not off the shelf product, it was designed by a hardware contractor, so I have do as you advised to change kernel+config and to add mtd-utils recipe. In my previous project working on a TI ARM processor with NOR Flash, installed with Debian

[yocto] Support NAND flash

Hi, Has anyone used NAND? Does the MTD already support the NAND driver or do you have to work our the detailed driver yourself? Could you share your experiences how to build the image and to hand and access the NAND if it is required? Thank you. Kind regards, - JH --

Re: [yocto] Issue with INCOMPATIBLE_LICENSE

FYI, On Fri, May 31, 2019 at 11:31:43AM +0200, Quentin Schulz wrote: > Hi all, > > We're in the middle of an upgrade to Thud 2.6.2. While doing so, we > blindly updated all upstream layers we use and we found out (during > integration phase, no need to send lawyers :) ) that even though we have

[yocto] arm yocto-linux custom defconfig not working

Hi, I have to create a custom 4.14.49 linux kernel. In my recipe I have added my defconfig , but yocto it's not taking in consideration the

Re: [yocto] arm yocto-linux custom defconfig not working

On Thu, Jun 6, 2019 at 9:38 AM Pierluigi Greto wrote: > > Hi, > > I have to create a custom 4.14.49 linux kernel. In my recipe I have added my > defconfig, but yocto it's not taking in consideration the defconfig. Instead > it's building the kernel using the default values. Also the compilation

Re: [yocto] arm yocto-linux custom defconfig not working

Hi Pierluigi, just to be clear, have you specified your defconfig in the SRC_URI of your kernel recipe? You can write an append file (that I guess you already did) and add: FILESEXTRAPATHS_prepend := "${THISDIR}/files:" SRC_URI_append= " file://defconfig" The above snippet assume that you are

Re: [yocto] Support NAND flash

More specific, looks to me that the drivers are OS based, the eCos has NAND I/O, the OpenWRT has some support NAND I/O as well, how does the Yocto support? Thank you. Kind regards, - JH On 6/6/19, JH wrote: > Hi, > > Has anyone used NAND? Does the MTD already support the NAND driver or > do

Re: [yocto] Support NAND flash

On Thu, Jun 06, 2019 at 09:15:46PM +1000, JH wrote: > More specific, looks to me that the drivers are OS based, the eCos has > NAND I/O, the OpenWRT has some support NAND I/O as well, how does the > Yocto support? This is not exactly a "how does the yocto" support-thing. Yocto is not the OS. The

[yocto] [meta-security][master][warrior][PATCH] bastille: solved the conflict with perl-module-text-wrap and base-files

-Remove the link to perl5 to resolve the conflict with perl-module-text-wrap. -Remove the operation on /var/lock to resolve the conflict with base-files. Signed-off-by: Zang Ruochen --- recipes-security/bastille/bastille_3.2.1.bb | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff

[yocto] How to set PACKAGE_EXTRA_ARCHS

Hi, I am facing an issue described here https://lists.yoctoproject.org/pipermail/yocto/2019-June/045565.html. I have come to the conclusion that I need to add armv7ahf-neon-mx8mm to PACKAGE_EXTRA_ARCHS but it is not obvious how to do that based on what is stated in the reference manual

[yocto] Minutes: Yocto Project Technical Team Meeting 6/4/2019

Yocto Project Technical Team Meeting MINUTES: 6/4/2019 Attendees: Richard, Armin, JoshuaW, Bruce, Michael, Randy, Scott, Alejandro, RobW, Ross, MichaelH, Tim, Vineela, David, Trevor, Sajal RP: * YP-2.6 M1 for this coming Monday * ptest dependencies are improving, and we are getting better

[yocto] [PATCH] utils.c: close all file descriptors after completing a ptest

vredir ptest fails since too many file descriptors were open. >From the failed ptest log: run-vredir 87,88c87,88 < ./vredir6.sub: line 10: /dev/null: Too many open files < ./vredir6.sub: line 13: /dev/null: Too many open files FAIL: run-vredir Added function to close file

[yocto] Necessary changes between SDK and eSDK builds

Hi I'm using yocto thud 2.6.1 always build & provide sdk's to our customers without problem. Now a customer requested an eSDK instead. According to the manual (https://www.yoctoproject.org/docs/2.1/sdk-manual/sdk-manual.html#sdk-building-an-sdk-installer), this should work identically by

[yocto] EMQ recipe

Hi, I'm the author of a Yocto Project layer called meta-erlang. I would like to announce that now is possible to use Yocto Project which build a embedded Linux distro and on top of that install the EMQ (a mqtt broker) or EMQ edge. I've created the recipe and all the patches necessary to do that.

Re: [yocto] [patchtest-oe][PATCH] test_metadata_src_uri: new unittest detecting added patch files without modifying SRC_URI

On Wed, 2019-05-29 at 10:28 +0800, Changqing Li wrote: > On 5/28/19 10:53 PM, akuster wrote: > > On 5/27/19 6:00 PM, Changqing Li wrote: > > > ping > > > > > > On 4/29/19 2:10 PM, Changqing Li wrote: > > > > ping > > > > > > Does this mean you have a working knowledge of patchtest? > > > > The

[yocto] Error in building new recipe for Jool network translator

Hi All, I'm new to yocto and I'm trying to create recipe for Jool network translator package. Tried to compile this package in manually and I'm able to compile with following steps. *Manual Steps:* ./autogen.sh ./configure make make install *Yocto Receipe: * DESCRIPTION = "Jool is an Open

Re: [yocto] Error in building new recipe for Jool network translator

Sounds like the makefiles are broken and can't handle out-of-tree builds. Try replacing inherit autotools with inherit autotools-brokensep (and if that fixes it, file a bug with jool as their build is broken). Ross On Thu, 6 Jun 2019 at 17:27, Gokul Raj wrote: > > Hi All, > > I'm new to yocto

Re: [yocto] Error in building new recipe for Jool network translator

Hi Ross, Thanks for the suggestion. I have tried with inheriting autotools-brokensep bbclass. Now bitbake got the path for compilation. But, bitbake compilation refering to native kernel src path for module compilation. For your information this package comes with both kernel module and userspace

Re: [yocto] Error in building new recipe for Jool network translator

On 6/6/19 11:46 AM, Gokul Raj wrote: > Hi Ross, > > Thanks for the suggestion. I have tried with inheriting autotools-brokensep > bbclass. Now bitbake got the path for compilation. But, bitbake compilation > refering to native kernel src path for module compilation. For your > information > this

Re: [linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

On Thu, 6 Jun 2019 at 10:16, Zumeng Chen wrote: > > > On 6/6/19 1:19 AM, Bruce Ashfield wrote: > > On Wed, Jun 5, 2019 at 4:02 AM Zumeng Chen > > wrote: > >> This patch is to add scc/cfg meta to build and boot zcu102 board with the > >> bsp > >> of xilinx-zynqmp. > >> > > See some questions

Re: [linux-yocto] [PATCH 1/1] xilinx-zynqmp: add the basic support xilinx-zynqmp

Yes, I checked it, it seems only for zynq 7000 and its special interfaces. I bet the original author didn't mean to share something for both arm64 and 32 :) When I created the structure I had intended for it to include the zynqmp related configs. I even had some yocto-kernel-cache patches