[yocto] Altera Cyclone V u-boot-spl with meta-altera

[Usman, Fahad]

Hi, I am using meta-altera layer (https://github.com/kraj/meta-altera) 
to build u-boot for Altera Cyclone V socfpga board. Building the 
u-boot-socfpga_2013.01.01 recipe does generate the u-boot-spl binary, 
but it cannot be directly used on the board as it has to be signed using 
Altera's tool "mkpimage" that comes with Altera's toolset (SoC EDS 
). 



Is there a way to produce a signed u-boot-spl image during the build, 
that can be used directly on the target without using the EDS?


Thanks,
Fahad.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Altera Cyclone V u-boot-spl with meta-altera

[Jon Szymaniak]

>
>
> If you upgrade to the U-Boot 2016.01 (or maybe even earlier?), mkimage
> actually supports adding the Bootrom signature to the SPL for you.  The
> current makefile is kind enough to concatenate the U-Boot SPL and its DTS
> for you, and then run mkpimage to create an 'spl/u-boot-spl-dts.sfp' file
> [1].
>
> If that doesn't work for you, you might find [2] to be useful.  The
> bootrom "signature" is simple enough to implement in a do_compile_append()
> or custom task.
>
> [1]
> http://git.denx.de/?p=u-boot.git;a=blob;f=Makefile;h=c9c2cbedc641853c7886ffb023e5798362152899;hb=6905f4d3c7be46fed4859f51f0a8f9a1107c22e7#l1012
>
> [2] https://github.com/maximeh/mkpimage
>
>
>
Typo correction: u-boot-with-spl-dtb.sfp
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Status WW04

[Philip Balister]

On 01/22/2016 11:29 AM, Jolley, Stephen K wrote:
>   *   I'd like to highlight that there are increasing numbers of stack 
> overflow questions about the project and help in providing good answers on 
> there would be appreciated.

We've been raising this issue the last few OpenEmbedded developer
meetings. There are a few people trying to answer questions there as we
have time. It takes time to build up enough reputation to be useful
there. Please people try and help out with this work. You should be able
to search on OpenEmbedded, Yocto, and Poky and get most of the questions.

Philip


>   *   WDD and bug trend continue to rise to new heights. We are simply 
> receiving more bugs than we have resources to fix/close.
> 
> Key YP 2.1 Dates:
> YP 2.1 M2 Cutoff (Feature Freeze) date is January 25, 2016 noon GMT
> YP 2.1 M2 Target release date is February 12, 2016
> YP 2.1 M3 Cutoff (Feature Freeze) date is February 29, 2016 noon GMT
> YP 2.1 M3 Target release date is March 18, 2016
> YP 2.1 M4 / Final Cutoff: March 28, 2016 noon GMT - Stabilization only 
> milestone.
> YP 2.1 Final Release Target: April 29, 2016
> 
> Key Status Links for YP:
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status
> https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule
> https://wiki.yoctoproject.org/wiki/Yocto_2.1_Features
> 
> Tracking Metrics:
> WDD 2581 (last week 2524 )
> (https://wiki.yoctoproject.org/charts/combo.html)
> 
> [If anyone has suggestions for other information you'd like to see on this 
> weekly status update, let us know!]
> 
> Thanks,
> 
> Stephen K. Jolley
> Yocto Project Program Manager
> INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
> *   Work Telephone:  (503) 712-0534
> *Cell:(208) 244-4460
> * Email: stephen.k.jol...@intel.com
> 
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Altera Cyclone V u-boot-spl with meta-altera

[Jon Szymaniak]

> Is there a way to produce a signed u-boot-spl image during the build, that
> can be used directly on the target without using the EDS?
>
>
If you upgrade to the U-Boot 2016.01 (or maybe even earlier?), mkimage
actually supports adding the Bootrom signature to the SPL for you.  The
current makefile is kind enough to concatenate the U-Boot SPL and its DTS
for you, and then run mkpimage to create an 'spl/u-boot-spl-dts.sfp' file
[1].

If that doesn't work for you, you might find [2] to be useful.  The bootrom
"signature" is simple enough to implement in a do_compile_append() or
custom task.

[1]
http://git.denx.de/?p=u-boot.git;a=blob;f=Makefile;h=c9c2cbedc641853c7886ffb023e5798362152899;hb=6905f4d3c7be46fed4859f51f0a8f9a1107c22e7#l1012

[2] https://github.com/maximeh/mkpimage
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-yocto][PATCH] poky-tiny: Use musl for default system C library

[Khem Raj]

> On Jan 17, 2016, at 11:04 PM, Khem Raj  wrote:
> 
>> 
>> On Jan 8, 2016, at 1:21 AM, Burton, Ross > > wrote:
>> 
>> 
>> On 8 January 2016 at 09:09, Burton, Ross > > wrote:
>> For anyone else reading, I just gave this a test locally, and for context 
>> the previous poky-tiny was using a tuned glibc and the rootfs came in at 
>> 1.5M.
>> 
>> Finished my comparison builds:
>> 
>> musl:
>> -rw-r--r-- 1 ross ross  731681 Jan  7 23:46 
>> core-image-minimal-qemux86-20160107234351.rootfs.cpio.gz
>> glibc:
>> -rw-r--r-- 1 ross ross 1569610 Jan  8 00:01 
>> core-image-minimal-qemux86-20160107235147.rootfs.cpio.gz
>> uclibc:
>> -rw-r--r-- 1 ross ross  669759 Jan  8 09:14 
>> core-image-minimal-qemux86-20160108090512.rootfs.cpio.gz
>> 
>> So it's a slightly increase over uclibc, but by default poky-tiny uses glibc 
>> so this is a massive win.  In the greater scheme of things musl is trending 
>> to be worth the increase over uclibc too.
>> 
> 
> Thanks Ross for this info. I think it will be interesting to know the sizes 
> of packages contributing to image from buildhistory if you have it lying 
> around.
> musl has libpthread/libm etc. all bundled into single .so for simplicity 
> reasons. I would like to get to bottom of the slight increase of musl over 
> uclibc based system
> 

musl/core-image-minimal ( 690K )

601 KiB busybox
598 KiB musl
23 KiB netbase
5 KiB update-rc.d
4 KiB update-alternatives-opkg
3 KiB busybox-udhcpc
3 KiB busybox-mdev
3 KiB base-files
2 KiB run-postinsts
2 KiB busybox-syslog

uclibc/core-image-minimal ( 614K)

603 KiB busybox
515 KiB uclibc
73  KiB libm1
23  KiB netbase
5   KiB update-rc.d
4   KiB update-alternatives-opkg
3   KiB busybox-udhcpc
3   KiB busybox-mdev
3   KiB base-files
2   KiB run-postinsts
2   KiB busybox-syslog


I don’t know why musl one is 690K where as the factored  sizes are quite same 
for both images . May be because it is on different machine.


> 
> 
>> Ross



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] /bin/release_scripts: Release automation scripts

[Graydon, Tracy]

[YOCTO #8942]

This is the initial commit of the release.py and misc component scripts which
form the basis for release automation work. The release.py script may be used
to stage and publish a major, point, or milestone release. The various
standalone scriptlet perform individual steps of parts of the release
 process and are handy for clean up, incremental staging, and testing.

Signed-off-by: Graydon, Tracy 
---
 bin/release_scripts/README  |  40 +++
 bin/release_scripts/convert_symlinks.py | 131 +
 bin/release_scripts/gen_md5.py  |  95 +++
 bin/release_scripts/nuke_cruft.py   |  92 +++
 bin/release_scripts/purge_unloved.py|  84 ++
 bin/release_scripts/release.py  | 475 
 bin/release_scripts/rsync.py| 176 
 7 files changed, 1093 insertions(+)
 create mode 100644 bin/release_scripts/README
 create mode 100755 bin/release_scripts/convert_symlinks.py
 create mode 100755 bin/release_scripts/gen_md5.py
 create mode 100755 bin/release_scripts/nuke_cruft.py
 create mode 100755 bin/release_scripts/purge_unloved.py
 create mode 100755 bin/release_scripts/release.py
 create mode 100755 bin/release_scripts/rsync.py

diff --git a/bin/release_scripts/README b/bin/release_scripts/README
new file mode 100644
index 000..dbc51fc
--- /dev/null
+++ b/bin/release_scripts/README
@@ -0,0 +1,40 @@
+The release.py script is intended to help more efficiently and consistently 
+publish releases. The script works for Major, Point, and Milestone releases.
+
+To invoke the script, run "python release.py . Available options are: 
 
+
+
+-i, --build-idRequired for all release types. Build id of release 
+  including rc#. i.e. yocto-2.0.rc1, yocto-2.1_M1.rc3, etc.
+-b, --branch  Required for Major and Point releases. i.e. daisy, fido, 
jethro, etc.
+-p, --poky-verRequired for Major and Point releases. Not used for 
Milestones. i.e. 14.0.0
+
+Example: 
+
+$ python release.py -i yocto-2.0.rc3 -b jethro -p 14.0.0 
+
+The script will take the release candidate name and determine the source and 
+target directories, as well as the type of release, etc., to prepare for 
staging 
+the release. 
+
+The script will then do the following:
+
+1) Rsync the rc candidate to a staging dir where all work happens
+2) Convert the symlink in build-appliance dir.
+3) In machines dir, convert the symlinks, delete the files we do not want to 
+   publish, and generate fresh md5sums after link conversion.
+4) For major and point releases, repackage the poky and eclipse tarballs using 
+   branch and poky version.
+5) For major and point releases, publish the eclipse plugins.
+6) For major and point releases, create the BSP tarballs. 
+7) For major and point releases, generate the master md5sum file for the 
release.
+8) Sync the staging directory to downloads directory.
+
+Currently, the ADT release sync and the release notes must still be done 
manually 
+and copied over to the release download directories accordingly. Future 
enhancements
+will address these two release steps.
+
+
+
+
+
diff --git a/bin/release_scripts/convert_symlinks.py 
b/bin/release_scripts/convert_symlinks.py
new file mode 100755
index 000..21aaf04
--- /dev/null
+++ b/bin/release_scripts/convert_symlinks.py
@@ -0,0 +1,131 @@
+import os
+import optparse
+import sys
+import hashlib
+import glob
+import os.path
+import shutil
+from shutil import rmtree, copyfile
+from subprocess import call
+
+def print_vars():
+print "AB_BASE: %s" %AB_BASE
+print "RELEASE_DIR: %s" %RELEASE_DIR
+print "MACHINES: %s" %MACHINES
+print
+return
+
+
+def get_list(dirname):
+dirlist = os.listdir(dirname)
+dirlist.sort()
+return dirlist
+
+def split_thing(thing, marker):
+filebits = thing.split(marker)
+return filebits
+
+def rejoin_thing(thing, marker):
+filebits = marker.join(thing)
+return filebits
+
+
+def convert_symlinks(dirname):
+thing = os.path.split(dirname)[1]
+if thing == "qemu":
+dirlist = get_list(dirname)
+for dir in dirlist:
+qemu_dir = os.path.join(MACHINES, dirname, dir)
+print "Converting symlinks in %s" %qemu_dir
+convert_symlinks(qemu_dir)
+else:
+print "Converting symlinks in %s" %dirname
+link_list = []
+for root, dirs, files in os.walk(dirname, topdown=True):
+for name in files:
+filename = (os.path.join(root, name))
+if os.path.islink(filename):
+src_file = os.path.realpath(filename)
+link_list.append([filename, src_file])
+for line in link_list:
+os.remove(line[0])
+try:
+   copyfile(line[1], line[0])
+except IOError:
+print "Error: %s is missing or isn\'t a real file" %line[1]
+else:
+   

Re: [yocto] Syslog Related testcases are failed in yocto LTP

[Yuki Machida]

Hi

> I build the LTP-2015-01-19 with yocto and I ran the runltp script on my board 
I got error with the syslog related test cases.
What it has happen error?
If it is possible to send a test log,
I may be able to give any advice for you.

Best regard,
Yuki Machida
On 2016年01月21日 21:10, Raghavendra Kakarla wrote:

Hi All,


I build the LTP-2015-01-19 with yocto and I ran the runltp script on my board I 
got error with the syslog related test cases.


Could please give me the some info such that I will resolve the issue.


Thanks in advance.


Regards,

Raghavendra K.




--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fixing packaging errors

[Christopher Larson]

On Thu, Jan 21, 2016 at 11:57 PM, Gary Thomas  wrote:

> ERROR: QA Issue: non -dev/-dbg/nativesdk- package contains symlink .so:
> graphviz path
> 'work/cortexa9hf-vfp-neon-amltd-linux-gnueabi/graphviz/2.38.0-r0/packages-split/graphviz/usr/lib/graphviz/libgvplugin_gd.so'
> [dev-so]
>
> Looking at the installed image, I see:
>
> $ ls -l
> tmp/work/cortexa9hf-vfp-neon-amltd-linux-gnueabi/graphviz/2.38.0-r0/image/usr/lib/graphviz/
> total 3016
> -rwxr-xr-x 3 gthomas gthomas1107 Jan 22 07:48 libgvplugin_core.la
> lrwxrwxrwx 1 gthomas gthomas  25 Jan 22 07:48 libgvplugin_core.so ->
> libgvplugin_core.so.6.0.0
> lrwxrwxrwx 1 gthomas gthomas  25 Jan 22 07:48 libgvplugin_core.so.6 ->
> libgvplugin_core.so.6.0.0
> -rwxr-xr-x 1 gthomas gthomas  341780 Jan 22 07:48
> libgvplugin_core.so.6.0.0
> -rwxr-xr-x 3 gthomas gthomas1143 Jan 22 07:48
> libgvplugin_dot_layout.la
> lrwxrwxrwx 1 gthomas gthomas  31 Jan 22 07:48
> libgvplugin_dot_layout.so -> libgvplugin_dot_layout.so.6.0.0
> lrwxrwxrwx 1 gthomas gthomas  31 Jan 22 07:48
> libgvplugin_dot_layout.so.6 -> libgvplugin_dot_layout.so.6.0.0
> -rwxr-xr-x 1 gthomas gthomas  616340 Jan 22 07:48
> libgvplugin_dot_layout.so.6.0.0
> -rwxr-xr-x 3 gthomas gthomas1451 Jan 22 07:48 libgvplugin_gd.la
> lrwxrwxrwx 1 gthomas gthomas  23 Jan 22 07:48 libgvplugin_gd.so ->
> libgvplugin_gd.so.6.0.0
> lrwxrwxrwx 1 gthomas gthomas  23 Jan 22 07:48 libgvplugin_gd.so.6 ->
> libgvplugin_gd.so.6.0.0
> -rwxr-xr-x 1 gthomas gthomas  141248 Jan 22 07:48 libgvplugin_gd.so.6.0.0
> -rwxr-xr-x 3 gthomas gthomas1155 Jan 22 07:48
> libgvplugin_neato_layout.la
> lrwxrwxrwx 1 gthomas gthomas  33 Jan 22 07:48
> libgvplugin_neato_layout.so -> libgvplugin_neato_layout.so.6.0.0
> lrwxrwxrwx 1 gthomas gthomas  33 Jan 22 07:48
> libgvplugin_neato_layout.so.6 -> libgvplugin_neato_layout.so.6.0.0
> -rwxr-xr-x 1 gthomas gthomas 1949008 Jan 22 07:48
> libgvplugin_neato_layout.so.6.0.0
> -rwxr-xr-x 3 gthomas gthomas2504 Jan 22 07:48 libgvplugin_rsvg.la
> lrwxrwxrwx 1 gthomas gthomas  25 Jan 22 07:48 libgvplugin_rsvg.so ->
> libgvplugin_rsvg.so.6.0.0
> lrwxrwxrwx 1 gthomas gthomas  25 Jan 22 07:48 libgvplugin_rsvg.so.6 ->
> libgvplugin_rsvg.so.6.0.0
> -rwxr-xr-x 1 gthomas gthomas   10764 Jan 22 07:48
> libgvplugin_rsvg.so.6.0.0
>
> I have two questions about this.
> * What is wrong with the setup of the libgvplugin_gd library
>   and how can I fix it?
>

Generally the .so for a normal library, non-plugin, is only required for
development. In this case, it's a plugin, so it'll be dlopen'd, so I expect
you could just opt-out of the QA check in this case.


> * All the rest of the libraries are set up the same.  Why don't
>   they get the same error?
>

IIRC there was a bug in the package qa bits which caused later messages to
suppress earlier due to teh use of a dictionary for the messages (the wrong
structure for this, no idea why it was done that way). There have been one
or more patches on teh list for this recently.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Altera Cyclone V u-boot-spl with meta-altera

[Randle, William C]

I’m not aware of a tool outside of Altera’s EDS mkpimage. What I ended up doing 
was installing a subset of the EDS tools (mkpimage and the jre directory), then 
tweaked the u-boot spl/Makefile to automatically invoke mkpimage to create the 
preloader. I also tweaked the meta-altera u-boot-socfpga.inc do_deploy() rules 
to copy the newly built preloader-mkpimage-* files to the deploy directory.

I’d be happy to send those to you, if you’re interested. Likewise, if you find 
a third party tool to add the preloader image header, let me know.

-Bill

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Usman, Fahad
Sent: Friday, January 22, 2016 7:19 AM
To: yvand...@opensource.altera.com; Khem Raj ; 
yocto@yoctoproject.org
Subject: [yocto] Altera Cyclone V u-boot-spl with meta-altera

Hi, I am using meta-altera layer (https://github.com/kraj/meta-altera) to build 
u-boot for Altera Cyclone V socfpga board. Building the 
u-boot-socfpga_2013.01.01 recipe does generate the u-boot-spl binary, but it 
cannot be directly used on the board as it has to be signed using Altera's tool 
"mkpimage" that comes with Altera's toolset (SoC 
EDS).

Is there a way to produce a signed u-boot-spl image during the build, that can 
be used directly on the target without using the EDS?

Thanks,
Fahad.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Question about sftp package

[Valentin Le bescond]

Hi !

I personally use :

IMAGE_INSTALL_append = " openssh-sftp-server"

in my image recipe.

cheers


Le ven. 22 janv. 2016 à 17:05, Max Sht  a écrit :

> Hi.
>
> Thank you in advance for your support.
> I'm using Yocto project Linux for the iMX6 CPU and imx6ulevk board.
>
> I've dowloaded and built the OS, but I having trouble activating the SFTP.
> I'm able to connect to the SSH but not the SFTP, which I need for
> uploading code using ECLIPSE. Is there a package that I need to add for
> SFTP support?
>
> I'm very to new to Linux, and hope that you can help me.
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Question about sftp package

[Randle, William C]

You will also want to make sure you are using openssh, rather than dropbear for 
ssh server and client. There are workarounds on the Internet for using dropbear 
and just build sftp-server from openssh package, but I had difficulty getting 
it to work and ended up just selecting openssh package instead, which included 
sftp-server by default. This was for poky daisy (1.6).

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Valentin Le bescond
Sent: Friday, January 22, 2016 8:17 AM
To: Max Sht ; yocto@yoctoproject.org
Subject: Re: [yocto] Question about sftp package

Hi !
I personally use :

IMAGE_INSTALL_append = " openssh-sftp-server"

in my image recipe.
cheers

Le ven. 22 janv. 2016 à 17:05, Max Sht 
> a écrit :
Hi.
Thank you in advance for your support.
I'm using Yocto project Linux for the iMX6 CPU and imx6ulevk board.
I've dowloaded and built the OS, but I having trouble activating the SFTP.
I'm able to connect to the SSH but not the SFTP, which I need for uploading 
code using ECLIPSE. Is there a package that I need to add for SFTP support?

I'm very to new to Linux, and hope that you can help me.

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Question about sftp package

[Max Sht]

Hi.

Thank you in advance for your support.
I'm using Yocto project Linux for the iMX6 CPU and imx6ulevk board.

I've dowloaded and built the OS, but I having trouble activating the SFTP.
I'm able to connect to the SSH but not the SFTP, which I need for uploading
code using ECLIPSE. Is there a package that I need to add for SFTP support?

I'm very to new to Linux, and hope that you can help me.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW04

[Jolley, Stephen K]

Current Dev Position: YP 2.1 M2
Next Deadline: YP 2.1 M2 Cutoff (Feature Freeze) date is January 25, 2016 noon 
GMT

SWAT team rotation: Randy -> Benjamin
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates:

  *   Yocto Project 2.0.1 was successfully built and is due out of QA soon, 
likely to release next week.
  *   Yocto Project 2.1 M2 cutoff is on Monday, please ensure any patches 
expected to be in M2 are sent to the mailing list for review before then.
  *   We are looking pretty up to date with patch review/processing although 
there is a large queue in -next pending final checks but which should merge 
soon.
  *   We are keeping an eye on CVEs and ensuring they get merged to various 
branches as we can find the bandwidth but we're low on manpower for this.
  *   I'd like to highlight that there are increasing numbers of stack overflow 
questions about the project and help in providing good answers on there would 
be appreciated.
  *   WDD and bug trend continue to rise to new heights. We are simply 
receiving more bugs than we have resources to fix/close.

Key YP 2.1 Dates:
YP 2.1 M2 Cutoff (Feature Freeze) date is January 25, 2016 noon GMT
YP 2.1 M2 Target release date is February 12, 2016
YP 2.1 M3 Cutoff (Feature Freeze) date is February 29, 2016 noon GMT
YP 2.1 M3 Target release date is March 18, 2016
YP 2.1 M4 / Final Cutoff: March 28, 2016 noon GMT - Stabilization only 
milestone.
YP 2.1 Final Release Target: April 29, 2016

Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.1_Features

Tracking Metrics:
WDD 2581 (last week 2524 )
(https://wiki.yoctoproject.org/charts/combo.html)

[If anyone has suggestions for other information you'd like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto