Re: [yocto-announce] Mailing list platform change November 21st

The window for the mailing list move has shifted forward to November 21st from 4pm to 8pm Pacific Standard Time. (2019-11-22 00:00-04:00 UTC) Moderators please tend to all pending requests today. Thank you, -- Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer On Fri

Re: [yocto] Mailing list platform change November 21st

The window for the mailing list move has shifted forward to November 21st from 4pm to 8pm Pacific Standard Time. (2019-11-22 00:00-04:00 UTC) Moderators please tend to all pending requests today. Thank you, -- Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer On Fri

[yocto-announce] Mailing list platform change November 21st

If there are serious issues we will rollback the changes. We will e-mail all lists when work is complete. -- Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer pEpkey.asc Description: application/pgp-keys -- ___ yocto-announce

Re: [linux-yocto] kernel-dev rpm does not have much contents

kernel-src. Let me know if this does not answer your question. Thank you again. Best Regards, Michael Y. Lim HW VPD Template Boston SFO Office: 045/C-08 Tie Line: 363-7244 Phone: (512) 286-7244 email: youh...@us.ibm.com -- ___ linux-yocto

Re: [linux-yocto] kernel-dev rpm does not have much contents

Why does it call kernel-devsrc instead of just kernel-dev? Is there a way to generate rpm for a complete kernel src with patches applied? Anyway, I really appreciate you spent your value time to help out. Best Regards, Michael Y. Lim HW VPD Template Boston SFO Office: 045/C-08 Tie Line: 363-7244 Ph

Re: [linux-yocto] [EXTERNAL] Re: kernel-dev rpm does not have much contents

>On Mon, Oct 28, 2019 at 11:36 AM Michael Lim wrote: >> >> I am building a power pc core-image-minimal in yocto using linux-yoct_4.19. The project was built successfully, However, the kernel-dev rpm does not have much content. >> >> Its contents below: >> fip

[linux-yocto] kernel-dev rpm does not have much contents

ew to the yocto build. Can someone help pointing out what I need to do to get all the code in ${STAGING_KERNEL_BUILDDIR} the kernel-dev rpm? By the way, I am using yocto 'WARRIOR' branch. Thank you in advance. Best Regards, Michael Y. Lim HW VPD Template Boston SFO Office: 045/C-0

[yocto] [yocto-autobuilder2][PATCH][v2] scheduler: make the default choice an option

The default choice on the force build form will select a random worker. builder_to_workers dictionary values can no longer be strings. Signed-off-by: Michael Halstead --- config.py | 4 ++-- schedulers.py | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/config.py b

[yocto] [yocto-autobuilder2][PATCH] scheduler: make the default choice an option

The default choice on the force build form will select a random worker. Updating to the corrent config. Note builder_to_workers dictionary values can no longer be strings. Signed-off-by: Michael Halstead --- config.py | 40 +++- schedulers.py | 2 +- 2

[linux-yocto] Mailing list update September 15th - platform change delayed

. Moderators, thanks for helping by clearing out the queues in advance. If you have outstanding moderation or trouble clearing your queue please reach out to me. I will send a follow up e-mail with a new time line for the platform change after these updates are in place. -- Michael Halstead Linux

[Yocto-bsp] Mailing list update September 15th - platform change delayed

. Moderators, thanks for helping by clearing out the queues in advance. If you have outstanding moderation or trouble clearing your queue please reach out to me. I will send a follow up e-mail with a new time line for the platform change after these updates are in place. -- Michael Halstead Linux

[yocto-announce] Mailing list update September 15th - platform change delayed

. Moderators, thanks for helping by clearing out the queues in advance. If you have outstanding moderation or trouble clearing your queue please reach out to me. I will send a follow up e-mail with a new time line for the platform change after these updates are in place. -- Michael Halstead Linux

[yocto] Mailing list update September 15th - platform change delayed

. Moderators, thanks for helping by clearing out the queues in advance. If you have outstanding moderation or trouble clearing your queue please reach out to me. I will send a follow up e-mail with a new time line for the platform change after these updates are in place. -- Michael Halstead Linux

[yocto-announce] Mailing list platform change September 15th

will rollback the changes. We will e-mail all lists when work is complete. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto-announce mailing list yocto-announce@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto-announce

[yocto] Mailing list platform change September 15th

will rollback the changes. We will e-mail all lists when work is complete. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[Yocto-bsp] Mailing list platform change September 15th

will rollback the changes. We will e-mail all lists when work is complete. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto-bsp mailing list yocto-bsp@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto-bsp

[yocto] kernel modul install

an bluetooth.ko which is already existing because of my linux-mainline recipe. What can i do? the relevant one is the one from my chip recipe.   Best regards, Michael -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo

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

On Thu, Jun 6, 2019 at 5:07 PM akuster808 wrote: > > > 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 > Yes f

[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 b5f600969

Re: [yocto] [yocto-infrastructure] Upcoming network outage: Fri, May 17 starting 10PM PDT (Sat, 5:00Z)

On 5/11/19 1:59 PM, akuster808 wrote: > > > On 5/10/19 4:21 PM, Michael Halstead wrote: >> What: 30-minute network outage to Portland-hosted services >> When: Fri, May 17, between 10PM-3AM PDT (Sat, 05:00-10:00 UTC) >> Why : Network equipment replacement by our serv

[yocto] Upcoming network outage: Fri, May 17 starting 10PM PDT (Sat, 5:00Z)

hosting provider needs to replace some of their main network equipment, which will require rerunning some cables. They are asking us to prepare for up to a 30-minute network outage between the hours listed above in order to complete this work. -- Michael Halstead Linux Foundation / SysAdmin

Re: [yocto] git.yoctoproject.org TLS certificate expired

cate. The > certificate expired on May 4, 2019, 7:53 AM. The current time is May 4, > 2019, 7:16 PM. > > > cu > Adrian I've renewed the certificate manually for now. I will review the automated process and monitoring to make sure this doesn't happen again. --

Re: [yocto] uboot-sign pyro fail

Hi On Thu, Mar 7, 2019 at 6:54 PM Michael Nazzareno Trimarchi wrote: > > Hi all > > I'm trying to generate a sign image with pyro but problem is that when > uboot is compiled > the build dir depend on UBOOT_CONFIG and when the uboot-sign.class try to find > the u-boot.dtb

[yocto] uboot-sign pyro fail

by uboot.inc. Anyone has some suggestions? Michael -- | Michael Nazzareno Trimarchi Amarula Solutions BV | | COO - Founder Cruquiuskade 47 | | +31(0)851119172 Amsterdam 1018 AM NL | | [`as] http

Re: [yocto] [OE-core] Yocto Project Status WW07'19

seems to be suffering from the 'outdated info' problem. For example glibc, or python3 recipes have been updated to latest versions, yet RRS still shows that they haven't been. We're reliant upon the layer index updating and it appears that's not working at the moment. I have asked Michael to look

Re: [yocto] [Recipe reporting system] Upgradable recipe name list

to mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [patchtest][PATCH] scripts: Reset working repository to match origin during clean up

Michael Halstead wrote: Since these commands run in $REPODIR and $path I think they will apply to any repository under test. On 1/11/19 12:25 PM, Khem Raj wrote: Hi Michael Can we enable these checks for meta-openembedded repo as well On Fri, Jan 11, 2019 at 11:03 AM Michael Halstead wrote

Re: [yocto] [patchtest][PATCH] scripts: Reset working repository to match origin during clean up

Since these commands run in $REPODIR and $path I think they will apply to any repository under test. On 1/11/19 12:25 PM, Khem Raj wrote: Hi Michael Can we enable these checks for meta-openembedded repo as well On Fri, Jan 11, 2019 at 11:03 AM Michael Halstead mailto:mhalst

[yocto] [patchtest][PATCH] scripts: Reset working repository to match origin during clean up

If the local HEAD is a patchtest generated merge commit patchtest may be unable to apply new patches. This should prevent patchtest from becoming stuck in that state. Signed-off-by: Michael Halstead --- scripts/create-share-folder | 2 +- scripts/host| 2 +- 2 files changed, 2

Re: [yocto] [Recipe reporting system] Upgradable recipe name list

reworking it, but Michael hasn't had the time to do the upgrade yet. I will ping him again. Cheers, Paul On Monday, 7 January 2019 11:35:01 PM NZDT Burton, Ross wrote: Yes, AUH pretty much replaces this I'd say. Ross On Mon, 7 Jan 2019 at 10:26, Alexander Kanavin wrote: Looks like this has

[yocto] Trying to use an external toolchain

t PROVIDES virtual/crypt but was skipped: Recipe only applies in nativesdk case for now glibc PROVIDES virtual/crypt but was skipped: Recipe is blacklisted: Using external toolchain Best regards Michael -- Hella Gutmann Solutions GmbH * Unternehmensform: Gesellschaft

[yocto] [yocto-autobuilder-helper][PATCH] config.json: Enable dedicated sstate during build and remove after

Without any sstate available oe-selftest cannot run in parallel. Set sstate to a location used only by these builds and remove it as the last step. Signed-off-by: Michael Halstead --- config.json | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/config.json b/config.json

Re: [yocto] [patchtest-oe][PATCH] test_patch_cve.py: fix cve tag checking logic

>> > Not sure if this is related but it looks like the tests aren't running > at all now ... > > > https://patchwork.openembedded.org/project/oe-core/series/?ordering=-last_updated > > Thanks, > > Anuj -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[yocto] [yocto-autobuilder-helper][PATCH] config.json: Disable BUILDINFO for oe-selftest

Currently the containerimage.ContainerImageTests.test_expected_files test doesn't expect a file at /etc/build so BUILDINFO must be false for the test to pass. Signed-off-by: Michael Halstead --- config.json | 1 + 1 file changed, 1 insertion(+) diff --git a/config.json b/config.json index

[yocto] [yocto-autobuilder-helper][PATCH] config.json: Remove sstate, add oe-selftest, and replace beaglebone

-by: Michael Halstead --- config.json | 17 ++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/config.json b/config.json index 2945155..abc5928 100644 --- a/config.json +++ b/config.json @@ -146,16 +146,27 @@ } }, "nightly-br

[yocto] [yocto-autobuilder-helper][PATCH] config.json: Add steps to test new workers before adding to the main pool

We add workers to the nightly-bringup pool to test them in a production like enviroment. Include one completely emulated target and one to test virtualization extentions. Signed-off-by: Michael Halstead --- config.json | 13 + 1 file changed, 13 insertions(+) diff --git

[yocto] [error-report-web][PATCH] Allow autobuilder filter string to match anywhere

Multiple build clusters use the same prefix so we match a more distinctive string anywhere in the submitter name. Signed-off-by: Michael Halstead --- Post/feed.py | 2 +- Post/views.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Post/feed.py b/Post/feed.py index

[yocto] QA notification for completed autobuilder build (yocto-2.6_M3.rc1)

: 8e791c40140460825956430ba86b6266fdec0a93 oecore: e3f5ceec690379d64bd38330111a32f6c8fc6353 poky: c6edf2f8bc5778b267e3a7f4e8875d22f359fb8d This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.pur...@linuxfoundation.org -- Michael Halstead

Re: [yocto] Error Report Tool Purge

Currently the database is 26GB. I'm going to start purging un-visited reports older than 180 days today. I see some good suggestions in this thread. Khem, would you open an enhancement request describing the counts you are interested in preserving? On Thu, Jul 19, 2018 at 11:08 PM Martin Jansa

[yocto] Capture download location and checksum?

As part of auditing, I'd like for the build to capture the download location. I am going to work on code that generates a license manifest that also includes the download location and checksum as part of the 'recipeinfo' file. Is this already saved off in a variable or other construct, or do I

Re: [yocto] Hook for layer-only actions?

oss > > On 10 July 2018 at 19:53, Alexander Kanavin > wrote: > > Yes. Implement a class and inherit it from the recipes. > > > > Alex > > > > 2018-07-10 20:50 GMT+02:00 Michael Habibi : > >> I was wondering if there is a way I can apply a global modifi

[yocto] Hook for layer-only actions?

I was wondering if there is a way I can apply a global modification to all recipes in a layer? For instance, we have our own layer for our changes that sit on top of the base Yocto/OE layers. What if, hypothetically, I wanted to insert a do_package_qa action globally, for everything in our layer.

Re: [yocto] Including a header from an external kernel module

On Tue., 10 Jul. 2018, 00:15 Andre McCurdy, wrote: > On Mon, Jul 9, 2018 at 3:07 PM, Michael Allwright > wrote: > > Yes, it ended up in the development package in the do_install_append > > attempt > > How did you confirm that (ie that the header ended up in th

Re: [yocto] Including a header from an external kernel module

workaround / hack so that it works... On Mon., 9 Jul. 2018, 19:47 Andre McCurdy, wrote: > On Mon, Jul 9, 2018 at 8:27 AM, Michael Allwright > wrote: > > Hello, > > > > I think it would be useful to extend the hello-mod recipe in > meta-skeleton > > to demonstra

[yocto] Including a header from an external kernel module

Hello, I think it would be useful to extend the hello-mod recipe in meta-skeleton to demonstrate some slightly more complicated scenarios. For example, I am trying to find out how to have two external kernel modules A and B, where module B #includes a header file provided by module A. I have

[yocto] Yocto SDK and license manifest

We use Yocto to generate a simple SDK that we use as a toolchain. However, it appears that building the SDK vs an image does not generate the license manifest (we have deploy/rpm, deploy/sdk, but not deploy/license). Have we configured something wrong, or perhaps do we need to do something

Re: [yocto] Generating license/manifest for a specific layer?

some text > manipulation in a ROOTFS_POSTPROCESS_COMMAND would be the way I'd > probably look at tackling it. > > On Wed, Jun 13, 2018 at 2:42 PM, Michael Habibi > wrote: > > Beth, > > > > This is for internal consumption. We want to be able to generate a full > > mani

Re: [yocto] Generating license/manifest for a specific layer?

Beth, This is for internal consumption. We want to be able to generate a full manifest, and also one that reflects how we diverged from base Yocto distribution. On Mon, Jun 11, 2018 at 10:55 AM Beth Flanagan wrote: > On Mon, Jun 11, 2018 at 2:46 PM, Michael Habibi > wrote: > >

[yocto] Generating license/manifest for a specific layer?

Our use case is to capture the license files, manifest (package/version), and download information only for packages we modify/add. We use our own layer to modify/add packages, everything coming from standard Yocto layers are untouched. Is there a way to generate this information on a

Re: [yocto] [Call to Action] Yocto Project Bug Triage

ar this week. > > > Original message ---- > From: Michael Halstead > Date: 5/29/18 8:37 AM (GMT-08:00) > To: Stephano Cetola , Trevor Woerner < > twoer...@gmail.com> > Cc: yocto@yoctoproject.org, "Jolley, Stephen K" < > stephen.k.jol.

Re: [yocto] [Call to Action] Yocto Project Bug Triage

On 05/29/2018 08:16 AM, Stephano Cetola wrote: > On 5/29/18 8:00 AM, Trevor Woerner wrote: >> Is someone working on putting together a (google?) calendar of the >> various project (OE Yocto) meetings? > Great question. > > Michael, do we have access to a Yocto Project

[yocto] [meta-qt4][PATCH] Qt4 fails to configure ICU with ICU6X.

Remove -std=gnu++98 from QMAKE_CXXFLAGS and add where necessary. Signed-off-by: Michael Gloff <mgl...@emacinc.com> --- recipes-qt4/qt4/qt4-4.8.7.inc | 3 ++- .../0037-fix-configure-with-icu60.patch | 26 +++ recipes-qt4/qt4/qt4-nati

Re: [yocto] Patching only the target version of a package?

, Burton, Ross <ross.bur...@intel.com> wrote: > On 1 February 2018 at 15:03, Michael Habibi <mikehab...@gmail.com> wrote: > >> So let's say my whole bbappend file is only necessary for the target >> version. Can I rename the whole thing package-target.bbapp

Re: [yocto] Patching only the target version of a package?

thing more specific? I have only seen -native, -cross, and some other ones that don't seem to apply to this case. On Thu, Feb 1, 2018 at 8:44 AM, Burton, Ross <ross.bur...@intel.com> wrote: > On 1 February 2018 at 14:29, Michael Habibi <mikehab...@gmail.com> wrote: > >> I'

[yocto] Patching only the target version of a package?

I'm sure this is really simple but I haven't quite wrapped my head around it. We have a bbappend file that supplies a set of patches. It currently has the unintended side-effect of patching both the native version used during the Yocto build process, and the eventual target version. How do I

Re: [yocto] Error do_compile libepoxy

Thanks Trevor - going in the right direction. There are no "GL" includes or libs in the recipe sysroot becuase userland does not provide it. Adding mesa-gl to DEPENDS allows it to complete. Not sure if this is the correct solution though. Michael Gloff On Thu, Jan 18, 2018 at 2:48

Re: [yocto] Error do_compile libepoxy

/glx_beginend | arm-poky-linux-gnueabi-gcc -o test/glx_beginend 'test/glx_beginend@exe/glx_beginend.c.o' '-Wl,--no-undefined' '-Wl,--as-needed' '-O2' '-pipe' '-g' '-feliminate-unused-debug-types' '-fdebug-prefix-map=/home/michael/oe/recipes/rpi-build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi

[yocto] Setting LDFLAGS for all packages

If not, does anybody of you know, how I could set the flag without breaking libtool? Thanks in advance Michael -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[yocto] Kernel Crash when moving from Pyro to Rocko (or master): change in kernel compile process or flags?

some of the features to test which one causes the issue? * * Any suspicions about what could cause this? * Pls. find a log of the crash below, and an excerpt of my kernel recipe and machine configuration. Thanks in advance for your help, Best regards, Michael - VFS: Mounted root

Re: [yocto] tiny-linux distribution with raspberrypi error

This looks to be because poky-tiny.conf does not allow overriding of the kernel provider. You could try the below patch to use a different kernel. Michael Gloff diff --git a/meta-poky/conf/distro/poky-tiny.conf b/meta-poky/conf/distro/poky-tiny.conf index 2032bfde32..acafd9fef4 100644 --- a/meta

Re: [yocto] Using site.conf

Ok thanks! I think I mistakenly thought that I needed to have it be called site.conf.sample, and it will copy the sample into the .conf file in the build/conf area. On Tue, Oct 31, 2017 at 9:24 AM, Burton, Ross <ross.bur...@intel.com> wrote: > On 31 October 2017 at 14:15, Michael Habibi

Re: [yocto] Using site.conf

Is there an example of this somewhere? I haven't had any luck in documentation or example code to see how to make the site.conf be used. On Mon, Oct 30, 2017 at 6:16 PM, Khem Raj <raj.k...@gmail.com> wrote: > On Fri, Oct 27, 2017 at 11:59 AM, Michael Habibi <mikehab...@gmail.

[yocto] Using site.conf

I'm a bit confused about the usage of site.conf. I see a sample in the poky distro area, but I'm not sure how this actually gets copied into a site.conf and actually used by deployed versions of our distribution. Is there some extra step I need to take to ensure site.conf.sample from my own

[yocto] [meta-raspberrypi][PATCH 3/3] bluez5: Replace /lib with ${nonarch_base_libdir}

From: Michael Gloff <mgl...@hotmail.com> Use standard variable name and avoid QA errors when usermerge DISTRO_FEATURE is enabled. Signed-off-by: Michael Gloff <mgl...@emacinc.com> --- recipes-connectivity/bluez5/bluez5_%.bbappend | 6 +++--- 1 file changed, 3 insertions(+),

[yocto] [meta-raspberrypi][PATCH 2/3] linux-raspberrypi: Replace /lib with ${nonarch_base_libdir}

From: Michael Gloff <mgl...@hotmail.com> Use standard variable name and avoid QA errors when usermerge DISTRO_FEATURE is enabled. Signed-off-by: Michael Gloff <mgl...@emacinc.com> --- recipes-kernel/linux/linux-raspberrypi.inc | 2 +- 1 file changed, 1 insertion(+), 1 delet

[yocto] [meta-raspberrypi][PATCH 1/3] linux-firmware: Replace /lib with ${nonarch_base_libdir}

From: Michael Gloff <mgl...@hotmail.com> Use standard variable name and avoid QA errors when usermerge DISTRO_FEATURE is enabled. Signed-off-by: Michael Gloff <mgl...@emacinc.com> --- recipes-kernel/linux-firmware/linux-firmware_%.bbappend | 8 1 fil

Re: [yocto] RFC: Backwards compatibility checking sstate-cache

suggestion, I was planning to cross-post when I had a more stable proof of concept code to share. Note: I'll be following my colleague, Mario Domenech Goulart (mario-goulart), to OEDEM 2017 where I hope to discuss the current concept code and show some potential use cases. Kind regards,

[yocto] Pruning poky-contrib Oct 1st

. - -- Michael Halstead Linux Foundation / SysAdmin -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEzowQ2UYmQerfiW8/amSWNbpCWpUFAlnKaMcACgkQamSWNbpC WpWw8hAAm+FTba/EK1NYz4CQJbTG08iiOPiqHm9oO8wlmAswigL6HrBJ5TDsgIVh FdkKcEpGhvHVlGfWZsUFAEUKayd4+5oCKg9zOST9/4lDc9SHbyAtf587POmVYVz2 P3r

Re: [yocto] [infra] git domain name updates

On 09/25/2017 06:17 PM, akuster808 wrote: > > > On 09/25/2017 05:17 PM, Michael Halstead wrote: >> Hello, >> >> As Yocto Project continues to grow load on our git server does as >> well. We are going to make a few changes to our git infrastructure to >>

Re: [yocto] [infra] git domain name updates

On 09/26/2017 03:27 AM, Burton, Ross wrote: > On 26 September 2017 at 01:17, Michael Halstead > <mhalst...@linuxfoundation.org <mailto:mhalst...@linuxfoundation.org>> > wrote: > > This is all ready to go right now. Please update your remotes. > Read-write u

[yocto] [infra] git domain name updates

This is all ready to go right now. Please update your remotes. We will have to make these changes required before we can start to get performance benefits from them. I suggest November 1st 2017 but I need more feedback before we can set a cut off date. Thank you, - -- Michael Halstead Yocto Project

Re: [yocto] downloads.yoctoproject.org timeouts and service interruptions

Dedicated hardware is now in place. This should resolve these issues. Please report any new timeouts in #yocto if possible. On 08/15/2017 10:27 AM, Michael Halstead wrote: > On Wednesday August 9th we upgraded the backend storage for > downloads.yoctoproject.org and related sites. T

[yocto] downloads.yoctoproject.org timeouts and service interruptions

now. Over the next day we will work to provision new decided resources for these important services. Expect timeouts and service interruptions for the next 24 hours. I will update the lists or you can follow the incident at https://status.linuxfoundation.org/incidents/hxz2f2kvbn88. -- Michael

Re: [yocto] Release Candidate Build for yocto-2.3.1.rc1 now available

The RC2 e-mail should arrive shortly. It was sent the normal way, directly by the autobuilder. On Wed, Jul 12, 2017 at 10:03 AM, Perez Carranza, Jose < jose.perez.carra...@intel.com> wrote: > Hi Michael > > You sent the mail for rc1 and there is an rc2 available, according to RP &

[yocto] Release Candidate Build for yocto-2.3.1.rc1 now available

5cd refkit : d86ed372d83a930e9fe2ef22e8a4b98a269d33e6 meta-mingw : 4bdb99650a053f254ccd158a6d0c25c80e79f6ee meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f meta-gplv2 : de001bd6bfcec943d274b649c62be6848cc9c3e6 poky : c2ef32ae58737463cf19aab7446d6a30ad81754f -- Michael Halstead Linux Foundation

Re: [yocto] RFC: Backwards compatibility checking sstate-cache

isions). Happy to answer in more detail if you require, just let me know. Thank you. Kind regards, Michael Ho -- BMW Car IT GmbH Michael Ho Spezialist Entwicklung - Linux Software Integration Lise-Meitner-Str. 14 89081 Ulm Tel.: +49 731 3780 4071 Mobil: +49 152 5498 0471 Fax: +49-731-37804-001

[yocto] RFC: Backwards compatibility checking sstate-cache

to make better use of the work already done there. The current implementation is a bit hacky but comments would be appreciated in regards to if the concept is feasible and if people are interested in making use of it and their use cases. Kind regards, Michael Ho -- BMW Car IT GmbH Michael Ho

Re: [yocto] [raspberrypi][rt] yocto Digest, Vol 81, Issue 118

PPER_ADDR@ > @PADDED_SPL_SIZE_BLOCKS@ > +echo Writing UBoot image to address 0x80 > +nand write @UBOOT_MEMIMG_ADDR@ @UBOOT_FLASH_ADDR@ @PADDED_UBOOT_SIZE@ > + > +# Setup the default environment > +setenv bootargs root=ubi0:rootfs rootfstype=ubifs rw earlyprintk ubi.mtd=4 > +setenv bootcmd_ubi 'mtdparts; ubi part UBI; ubifsmount ubi0:rootfs; > ubifsload \$fdt_addr_r /boot/sun5i-r8-chip.dtb; ubifsload \$kernel_addr_r > /boot/zImage; bootz \$kernel_addr_r - \$fdt_addr_r' > +setenv boot_targets fel ubi usb0 pxe dhcp > +setenv fel_booted 0 > + > +echo Enabling Splash > +setenv stdout serial > +setenv stderr serial > +setenv splashpos m,m > + > +echo Setting Video Mode > +setenv video-mode > sunxi:640x480-24@60,monitor=composite-ntsc,overscan_x=40,overscan_y=20 > + > +echo Saving default environment > +saveenv > + > +echo Writing UBI rootfs to NAND address 0x100 > +nand write.slc-mode.trimffs @UBI_MEMIMG_ADDR@ @UBI_FLASH_ADDR@ @UBI_SIZE@ > + > + > +echo === > +echo Flashing Complete. Please power down and disable FEL mode. > +echo === > + > +# Loop continually flashing the status LED > +while true ; do > +mw.l @SPL_MEMIMG_ADDR@ 0x 1 > +i2c write @SPL_MEMIMG_ADDR@ @LED_I2C_CHIP@ @LED_I2C_ADDR@ 4 > +sleep 1 > Date: Sun, 25 Jun 2017 19:32:36 -0700 > From: "Paul D. DeRocco" <pdero...@ix.netcom.com> > To: <yocto@yoctoproject.org> > Subject: [yocto] Current state of linux-raspberrypi-rt? > Message-ID: <23EE2924AFA4488992A7D0127F20147A@PAULD> > Content-Type: text/plain; charset="iso-8859-1" > > Google turns up a lot of stuff about this, but the latest I found was a > thread from 1/5/17 that started with Trevor Woerner posting a 1MB patch, > and that ended with him posting a message saying that it didn't actually > work. > > Is there anything new on this? I'm trying to do some compute-intensive > audio on an RPi3, and it really needs a real-time kernel. > > -- > > Ciao, Paul D. DeRocco > Paulmailto:pdero...@ix.netcom.com I am using at the moment the raspberrypi and was able to patch with a rt patch downloaded from https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.9/ Patching, Configuring, compiling. All seems to work. Having booted the Pi i can see via uname -a, that the rt-patch is applied. The performance seems to be very nice. What is google doing about this? kind regards Michael Wiesing -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Wireshark but no Tshark?

I was able to create a username and password, and use this as credentials for SSH. However, I can't run some of the commands that I can when using picocom, and thus operating as root. On Mon, Jun 12, 2017 at 10:34 AM, Michael Calve <michael.ca...@vectare.com> wrote: > Okay thank you

[yocto] mkfifo: not found

Hello, I upgraded from poky 2.1 to 2.3 and now I have an issue with mkfifo in a do_install step. The error is "mkfifo: not found" I already added the package coreutils as dependency. Does someone has some hints for me? Regards Michael -- ___

Re: [yocto] Wireshark but no Tshark?

at 20:59, Michael Calve <michael.ca...@vectare.com> wrote: > >> Hi, I've seen that Wireshark is portable to Yocto, however Tshark is >> not? Is there other/better software for reading pcaps and getting field >> data??? >> > > Hi, > > tshark is part of

[yocto] Wireshark but no Tshark?

Hi, I've seen that Wireshark is portable to Yocto, however Tshark is not? Is there other/better software for reading pcaps and getting field data??? Sincerely, Michael -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org

[yocto] Show cmake warnings as yocto warnings

Hello, I am using cmake in my recipes (poky 2.1.2). Is there a way to display cmake warnings as yocto warnings? I can see the cmake warning in the log.do_configure file of my package but it is not displayed prominent during bitbake. Cheers and many thanks in advance, Michael

[yocto] [infra] Intermittent outages for Yocto Project services starting soon

PDT / 13:00 UTC Apologies for the short notice. -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[yocto] Compiling with armcc for yocto

Hi, I have an application which I built using the poky toolchain for yocto on a BeagleboneBlack device. I would like to build my application with armcc. I read that you can build with armcc a linux application, is it possible to do it for yocto as well? Thanks, Michael IMPORTANT NOTICE

[yocto] Using armcc in Yocto

? Thanks, Michael Schwarcz IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store

Re: [yocto] Changing over to systemd (no dhcp)

wn or reboot: echo "Sending all processes the TERM signal..." killall5 -15 sleep 5 echo "Sending all processes the KILL signal..." killall5 -9 Reducing to 1 or 2 seconds should be sufficient. Michael Gloff > > > Kind regards, > > Mike Looijm

Re: [yocto] [bitbake-devel] [oe] Infra Full Stop 12/26-12/29

On 12/25/2016 11:43 PM, Martin Jansa wrote: > On Sun, Dec 25, 2016 at 08:06:50PM -0800, Michael Halstead wrote: >> In preparation for the scheduled maintenance I have moved >> git.openembedded.org to a new server temporarily. E-mail and Patchwork >> hooks may not work cor

Re: [yocto] [oe] Infra Full Stop 12/26-12/29

_ >>> Openembedded-devel mailing list >>> openembedded-de...@lists.openembedded.org >>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel >> -- >> ___ >> Openembedded-devel mai

[yocto] curl-native and ca-bundle

/cert.pem \ "$cac"; do if test -f "$a"; then ca="$a" break fi done Regarding this configuration script, removing --with-ca-bundle in curl-native should not cause any problems. Kind regards Michael -Ursprüngliche Na

Re: [yocto] curl-native and ca-bundle

Hi Patrick What do you think of removing the --with-ca-bundle as a solution for curl-native? On my machine it works without problems. Might this be an acceptable solution for upstream? Kind regards Michael -Ursprüngliche Nachricht- Von: Patrick Ohly [mailto:patrick.o...@intel.com

[yocto] curl-native and ca-bundle

I removed the "--with-ca-bundle" configure option in native builds and curl is now loading the default certificate chain of the build host. Does anybody found simmilar issues in other recipes? How do you handle them? Is there a common approach? K

Re: [yocto] Two pythons

ss <ross.bur...@intel.com> wrote: >> >> On 12 October 2016 at 18:58, Michael Callahan <coder.calla...@gmail.com> >> wrote: >>> >>> I just moved my project from Fido to Krogoth and now I have two >>> pythons (2.7 and 3). This bumps the size of

[yocto] Two pythons

code for that one but I suppose with enough work I could get all of the python2 code working with python3. Michael -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[yocto] Proper way of rebuilding kernel image

Hi, I am compiling Yocto kernel image with: * a third party's "in-tree" kernel configuration * the same third party's BSP (which has some further kernel configurations as well) * my own kernel configuration fragments for my project on top of the above two What I found was if I make a small

[yocto] fetch artifacts from Artifactory

empting MIRRORS if available ERROR: xx-1.0-r0 do_fetch: Fetcher failure: Fetch command failed with exit code 6, output: Authorization failed. " I tried to remove the 'user' and 'pswd' option, the same error returned. What's the correct syntax for fetching artifacts? Thanks fo

[yocto] Git/yocto newbie question re: submodules and multiple layers

Hi, I am well-versed with Git but I haven't really ever had to use submodules. I am trying to create a git repository on our server that will host our yocto distribution. Our distribution will include the yocto repo, plus meta-openembedded repo, plus maybe some other layers. The difficulty I have

[yocto] Building applications and distributions separately, but integrate into final image

All, I am looking at Yocto as a replacement for our embedded distribution. Currently we build everything as a distribution. This includes building the Linux kernel, open source packages, as well as our own IP and applications. As you can imagine, a vast majority of our build is taken up by

Re: [yocto] Trying to run toaster off master, running into issues w/ django

Excellent. Thanks! I knew using latest was going to burn me eventually :) On Wed, Aug 24, 2016 at 5:51 AM, Ed Bartosh <ed.bart...@linux.intel.com> wrote: > On Tue, Aug 23, 2016 at 04:49:42PM -0500, Michael Habibi wrote: >> I am running the master branch and trying to run toaster to

[yocto] devtool build fails the second time

Hi, I want to use `devtool modify ' to modify the source code and create patches. already contains some source patches. My workflow looks like this: devtool modity Fetching, Unpacking, Patching  all works devtool build devtool build fails during compile task, that's expected and that's

  1   2   3   >