date:20170103

[yocto] OpenEmbedded Stand at FOSDEM

2017-01-03 Thread Philip Balister

Every year since 2007, OpenEmbedded has a stand at FOSDEM
(http://www.fosdem.org)

>From the first year:

https://www.flickr.com/photos/32615155@N00/405229708/in/album-72157594561002629/

Belen and I are sort of organizing this, but both of us are also
involved in devrooms, so we will need a lot of help manning the stand
and getting some demos together.

Demos should try and show how the project makes embedded work easier, by
showing tools and/or cool examples of devices using Linux built with
OpenEmbedded. In previous years, we've shown toaster with data collected
from demos on the table. Collections of devices running images built
from the same recipe and interesting products using Linux by OpenEmbedded.

I'm happy to try and organize demos and staffing, but I could really use
some help this year, so if you are in a position to tak ethe lead on
operating the stand, that would be a huge help to me and the rest of the
project.

Thanks,

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

[yocto] Yocto Project Status WW01

2017-01-03 Thread Jolley, Stephen K

Current Dev Position: YP 2.3 M2 -> M3

Next Deadline: YP 2.3 M2 by Jan 23, 2017


SWAT team rotation: Maxin -> Joshua

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

*M1 is having some QA difficulties due to some kind of bad interaction 
between the PR service and tinfoil2. We're waiting until people are back from 
vacation and up to speed before we decide what to do about this.

*Both Ross and Richard decided to spend time away from computers over 
the holidays so things have not really changed much over the past couple of 
weeks, there is a small backlog of patches pending which will be worked through 
this week.

*M2 will be upon us sooner than we realize and there are some key 
changes such as recipe specific sysroots pending with some potential for 
disruption. Wider testing of these patch sets as they're published would be 
appreciated.


Proposed upcoming dot releases:

YP 2.2.1 Release by Jan. 20, 2017

YP 2.1.3 Release by May. 19, 2017


Key YP 2.3 Dates:

YP 2.3 M1 Release is Dec. 23, 2016

YP 2.3 M2 Cutoff is Jan. 23, 2017

YP 2.3 M2 Release is Feb. 3, 2017

YP 2.3 M3 Cutoff is Feb 27, 2017

YP 2.3 M3 Release is Mar. 10, 2017

YP 2.3 M4 Cutoff is April 3, 2017

YP 2.3 M4 Release is April 28, 2017


Tracking Metrics:

WDD 2594 (last week 2559)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features

[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

[yocto] Yocto Project Status WW01

2017-01-03 Thread Jolley, Stephen K

Current Dev Position: YP 2.3 M2 -> M3

Next Deadline: YP 2.3 M2 by Jan 23, 2017


SWAT team rotation: Maxin -> Joshua

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

*M1 is having some QA difficulties due to some kind of bad interaction 
between the PR service and tinfoil2. We're waiting until people are back from 
vacation and up to speed before we decide what to do about this.

*Both Ross and Richard decided to spend time away from computers over 
the holidays so things have not really changed much over the past couple of 
weeks, there is a small backlog of patches pending which will be worked through 
this week.

*M2 will be upon us sooner than we realize and there are some key 
changes such as recipe specific sysroots and the oeqa framework rework pending 
with some potential for disruption. Wider testing of these patch sets as 
they're published would be appreciated.


Proposed upcoming dot releases:

YP 2.2.1 Release by Jan. 20, 2017

YP 2.1.3 Release by May. 19, 2017


Key YP 2.3 Dates:

YP 2.3 M1 Release is Dec. 23, 2016

YP 2.3 M2 Cutoff is Jan. 23, 2017

YP 2.3 M2 Release is Feb. 3, 2017

YP 2.3 M3 Cutoff is Feb 27, 2017

YP 2.3 M3 Release is Mar. 10, 2017

YP 2.3 M4 Cutoff is April 3, 2017

YP 2.3 M4 Release is April 28, 2017


Tracking Metrics:

WDD 2594 (last week 2559)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features


[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

[yocto] [opkg-utils PATCH] Added support to generate index file with multiple version per package

2017-01-03 Thread Desmond Correia

>From aefa378d6a167124bdfb0b8d6c92aadb4c36fa46 Mon Sep 17 00:00:00 2001
From: Desmond 
Date: Wed, 28 Dec 2016 13:16:48 -0500
Subject: [opkg-utils PATCH] Added support to generate index file with
multiple
 version per package
To: opkg-de...@googlegroups.com,
yocto@yoctoproject.org

Using the -a option with opkg-make-index, you can now generate an index
file which will list multiple version of the same package. Added since opkg
now supports specifying version of package.
---
 opkg-make-index | 16 
 opkg.py |  8 +++-
 2 files changed, 19 insertions(+), 5 deletions(-)

diff --git a/opkg-make-index b/opkg-make-index
index 7897918..3f757f6 100755
--- a/opkg-make-index
+++ b/opkg-make-index
@@ -11,7 +11,7 @@ import re
 verbose = 0

 def usage():
- sys.stderr.write("%s [-h] [-s] [-m] [-l Packages.filelist] [-p
Packages] [-r Packages.old] [-L localesdir] [-v] packagesdir\n" %
(sys.argv[0],))
+ sys.stderr.write("%s [-h] [-s] [-m] [-a] [-l Packages.filelist] [-p
Packages] [-r Packages.old] [-L localesdir] [-v] packagesdir\n" %
(sys.argv[0],))
  sys.exit(-1)

 def to_morgue(filename):
@@ -42,7 +42,8 @@ filelist_filename = None
 stamplist_filename = "Packages.stamps"
 opt_s = 0
 opt_m = 0
-(opts, remaining_args) = getopt.getopt(sys.argv[1:], "hl:p:vsmr:L:")
+opt_a = 0
+(opts, remaining_args) = getopt.getopt(sys.argv[1:], "hl:p:vsmr:L:a")
 for (optkey, optval) in opts:
  if optkey == '-h':
   usage()
@@ -61,6 +62,8 @@ for (optkey, optval) in opts:
   old_filename = optval
  if optkey == '-L':
   locales_dir = optval
+ if optkey == '-a':
+  opt_a = 1

 if ( not remaining_args ):
  usage()
@@ -120,12 +123,17 @@ for abspath in files:
   if (verbose):
sys.stderr.write("Reading info for package %s\n" %
(filename,))
   pkg = opkg.Package(abspath, relpath=pkg_dir)
- pkg_key = ("%s:%s" % (pkg.package, pkg.architecture))
+
+ if opt_a:
+  pkg_key = ("%s:%s:%s" % (pkg.package, pkg.architecture,
pkg.version))
+ else:
+ pkg_key = ("%s:%s" % (pkg.package, pkg.architecture))
+
  if (pkg_key in packages.packages):
   old_filename = packages.packages[pkg_key].filename
  else:
   old_filename = ""
- s = packages.add_package(pkg)
+ s = packages.add_package(pkg, opt_a)
  pkgsStamps[filename] = fnameStat.st_mtime
  if s == 0:
   if old_filename:
diff --git a/opkg.py b/opkg.py
index b0d79a6..47473da 100644
--- a/opkg.py
+++ b/opkg.py
@@ -501,10 +501,16 @@ class Packages(object):
 self.packages = {}
 return

-def add_package(self, pkg):
+def add_package(self, pkg, opt_a=0):
 package = pkg.package
 arch = pkg.architecture
 name = ("%s:%s" % (package, arch))
+ver = pkg.version
+if opt_a:
+name = ("%s:%s:%s" % (package, arch, ver))
+else:
+name = ("%s:%s" % (package, arch))
+
 if (name not in self.packages):
 self.packages[name] = pkg

-- 
2.7.4
From aefa378d6a167124bdfb0b8d6c92aadb4c36fa46 Mon Sep 17 00:00:00 2001
From: Desmond 
Date: Wed, 28 Dec 2016 13:16:48 -0500
Subject: [opkg-utils PATCH] Added support to generate index file with multiple
 version per package
To: opkg-de...@googlegroups.com,
yocto@yoctoproject.org

Using the -a option with opkg-make-index, you can now generate an index file which will list multiple version of the same package. Added since opkg now supports specifying version of package.
---
 opkg-make-index | 16 
 opkg.py |  8 +++-
 2 files changed, 19 insertions(+), 5 deletions(-)

diff --git a/opkg-make-index b/opkg-make-index
index 7897918..3f757f6 100755
--- a/opkg-make-index
+++ b/opkg-make-index
@@ -11,7 +11,7 @@ import re
 verbose = 0
 
 def usage():
- sys.stderr.write("%s [-h] [-s] [-m] [-l Packages.filelist] [-p Packages] [-r Packages.old] [-L localesdir] [-v] packagesdir\n" % (sys.argv[0],))
+ sys.stderr.write("%s [-h] [-s] [-m] [-a] [-l Packages.filelist] [-p Packages] [-r Packages.old] [-L localesdir] [-v] packagesdir\n" % (sys.argv[0],))
  sys.exit(-1)
 
 def to_morgue(filename):
@@ -42,7 +42,8 @@ filelist_filename = None
 stamplist_filename = "Packages.stamps"
 opt_s = 0
 opt_m = 0
-(opts, remaining_args) = getopt.getopt(sys.argv[1:], "hl:p:vsmr:L:")
+opt_a = 0
+(opts, remaining_args) = getopt.getopt(sys.argv[1:], "hl:p:vsmr:L:a")
 for (optkey, optval) in opts:
  if optkey == '-h': 
   usage()
@@ -61,6 +62,8 @@ for (optkey, optval) in opts:
   old_filename = optval
  if optkey == '-L':
   locales_dir = optval
+ if optkey == '-a':
+  opt_a = 1
 
 if ( not remaining_args ):
  usage()
@@ -120,12 +123,17 @@ for abspath in files:
   if (verbose):
sys.stderr.write("Reading info for package %s\n" % (filename,))
   pkg = opkg.Package(abspath, relpath=pkg_dir)
- pkg_key = ("%s:%s" %

Re: [yocto] [opkg-devel] [opkg-utils PATCH] Added support to generate index file with multiple version per package

2017-01-03 Thread Desmond Correia

Hi Alejandro,

Thanks for catching that see attached.



On Fri, Dec 30, 2016 at 12:21 PM, Alejandro del Castillo <
alejandro.delcasti...@ni.com> wrote:

> Hi Desmond, thanks for sending the patch, works as expected.
>
> The only thing missing is your Signed-off-by line, do you mind resending
> with it?
>
> I also have a very minor comment below
>
> On 12/28/2016 01:15 PM, Desmond Correia wrote:
> > From aefa378d6a167124bdfb0b8d6c92aadb4c36fa46 Mon Sep 17 00:00:00 2001
> > From: Desmond  > >
> > Date: Wed, 28 Dec 2016 13:16:48 -0500
> > Subject: [opkg-utils PATCH] Added support to generate index file with
> > multiple
> >  version per package
> > To: opkg-de...@googlegroups.com ,
> > yocto@yoctoproject.org 
> >
> > Using the -a option with opkg-make-index, you can now generate an index
> > file which will list multiple version of the same package. Added since
> > opkg now supports specifying version of package.
> > ---
> >  opkg-make-index | 16 
> >  opkg.py |  8 +++-
> >  2 files changed, 19 insertions(+), 5 deletions(-)
> >
> > diff --git a/opkg-make-index b/opkg-make-index
> > index 7897918..3f757f6 100755
> > --- a/opkg-make-index
> > +++ b/opkg-make-index
> > @@ -11,7 +11,7 @@ import re
> >  verbose = 0
> >
> >  def usage():
> > - sys.stderr.write("%s [-h] [-s] [-m] [-l Packages.filelist] [-p
> > Packages] [-r Packages.old] [-L localesdir] [-v] packagesdir\n" %
> > (sys.argv[0],))
> > + sys.stderr.write("%s [-h] [-s] [-m] [-a] [-l Packages.filelist]
> > [-p Packages] [-r Packages.old] [-L localesdir] [-v] packagesdir\n" %
> > (sys.argv[0],))
> >   sys.exit(-1)
> >
> >  def to_morgue(filename):
> > @@ -42,7 +42,8 @@ filelist_filename = None
> >  stamplist_filename = "Packages.stamps"
> >  opt_s = 0
> >  opt_m = 0
> > -(opts, remaining_args) = getopt.getopt(sys.argv[1:], "hl:p:vsmr:L:")
> > +opt_a = 0
> > +(opts, remaining_args) = getopt.getopt(sys.argv[1:], "hl:p:vsmr:L:a")
> >  for (optkey, optval) in opts:
> >   if optkey == '-h':
> >usage()
> > @@ -61,6 +62,8 @@ for (optkey, optval) in opts:
> >old_filename = optval
> >   if optkey == '-L':
> >locales_dir = optval
> > + if optkey == '-a':
> > +  opt_a = 1
> >
> >  if ( not remaining_args ):
> >   usage()
> > @@ -120,12 +123,17 @@ for abspath in files:
> >if (verbose):
> > sys.stderr.write("Reading info for package %s\n" %
> > (filename,))
> >pkg = opkg.Package(abspath, relpath=pkg_dir)
> > - pkg_key = ("%s:%s" % (pkg.package, pkg.architecture))
> > +
> > + if opt_a:
> > +  pkg_key = ("%s:%s:%s" % (pkg.package, pkg.architecture,
> > pkg.version))
> > + else:
> > + pkg_key = ("%s:%s" % (pkg.package, pkg.architecture))
> > +
> >   if (pkg_key in packages.packages):
> >old_filename = packages.packages[pkg_key].filename
> >   else:
> >old_filename = ""
> > - s = packages.add_package(pkg)
> > + s = packages.add_package(pkg, opt_a)
> >   pkgsStamps[filename] = fnameStat.st_mtime
> >   if s == 0:
> >if old_filename:
> > diff --git a/opkg.py b/opkg.py
> > index b0d79a6..47473da 100644
> > --- a/opkg.py
> > +++ b/opkg.py
> > @@ -501,10 +501,16 @@ class Packages(object):
> >  self.packages = {}
> >  return
> >
> > -def add_package(self, pkg):
> > +def add_package(self, pkg, opt_a=0):
> >  package = pkg.package
> >  arch = pkg.architecture
> >  name = ("%s:%s" % (package, arch))
>
> since you are defining name on the else case, you can delete the line above
>
> > +ver = pkg.version
> > +if opt_a:
> > +name = ("%s:%s:%s" % (package, arch, ver))
> > +else:
> > +name = ("%s:%s" % (package, arch))
> > +
> >  if (name not in self.packages):
> >  self.packages[name] = pkg
> >
> > --
> > 2.7.4
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "opkg-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to opkg-devel+unsubscr...@googlegroups.com
> > .
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> Cheers,
>
> Alejandro
>



-- 

Desmond Correia
From bba7ceafaebe2fdd213fd1298b4f9760fafedda9 Mon Sep 17 00:00:00 2001
From: desmond 
Date: Fri, 30 Dec 2016 12:35:27 -0500
Subject: [opkg-utils PATCH] Added support to generate index file with multiple
 version per package
To: opkg-de...@googlegroups.com,
yocto@yoctoproject.org

Signed-off-by: desmond 
Using the -a option with opkg-make-index, you can now generate an index file which will list multiple version of the same package. Added since opkg now supports specifying version of package.
---
 opkg-make-index | 16

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Jan. 3, 2017 8:00 AM US Pacific Time

2017-01-03 Thread Jolley, Stephen K

Attendees: Stephen, Saul, Richard, Joshua, Stephano, Michael,



* Opens collection - 5 min (Stephen)

* Yocto Project status - 5 min (Stephen/team)

YP 2.3 M1 was built - Some problems were found in QA.  Due to the holidays 
little progress was made in fixing the issues.  We are hoping to get it fixed 
soon.

YP 2.2.1 was targeted to be built 1/9/17, but will be pushed while we focus on 
M1.  No new target yet.  It might be pushed beyond M2.

YP 2.3 M2 is cut off is 1/23/17.

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features

* Opens - 10 min

We discussed if we should branch M1 and make the fixes, or take master (which 
has some enchantments past M1.)  It will be discussed on the mailing list.

* Team Sharing - 10 min


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] [OE-core] Yocto Project Status WW01

2017-01-03 Thread Richard Purdie

On Tue, 2017-01-03 at 15:51 +, Jolley, Stephen K wrote:
> Current Dev Position: YP 2.3 M2 -> M3
> Next Deadline: YP 2.3 M2 by Jan 23, 2017
>  
> SWAT team rotation: Maxin -> Joshua
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>  
> Key Status/Updates:
> ·    M1 is having some QA difficulties due to some kind of bad
> interaction between the PR service and tinfoil2. We’re waiting until
> people are back from vacation and up to speed before we decide what
> to do about this.

One question which came up was whether just to cherry-pick fixes for M1
into a branch, or whether we use master. For me personally master is
tempting but its probably safer just to use an M1 branch as master has
moved on a fair bit. I wanted to give people an opportunity to express
opinions either way.

Cheers,

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

[yocto] [meta-oic][PATCH 1/3] meta-oic: Hotfix to support aarch64 for DragonBoard-410c

2017-01-03 Thread Philippe Coval

Apply patch from iotivity-1.2.1:

* [PATCH 081/341] yocto: Add aarch64 for DragonBoard-410c

Bug-AGL: SPEC-158
Change-Id: I06f56ae860760002a6376866488e1f55624f50cc
Origin: https://gerrit.automotivelinux.org/gerrit/#/c/7981/
Signed-off-by: Philippe Coval 
---
 ...81-yocto-Add-aarch64-for-DragonBoard-410c.patch | 48 ++
 recipes-core/iotivity/iotivity_1.2.0.bb|  1 +
 2 files changed, 49 insertions(+)
 create mode 100644 
recipes-core/iotivity/files/0081-yocto-Add-aarch64-for-DragonBoard-410c.patch

diff --git 
a/recipes-core/iotivity/files/0081-yocto-Add-aarch64-for-DragonBoard-410c.patch 
b/recipes-core/iotivity/files/0081-yocto-Add-aarch64-for-DragonBoard-410c.patch
new file mode 100644
index 000..08c93f6
--- /dev/null
+++ 
b/recipes-core/iotivity/files/0081-yocto-Add-aarch64-for-DragonBoard-410c.patch
@@ -0,0 +1,48 @@
+From 6554de025f4819f9f458cde70d706beab3ed11b8 Mon Sep 17 00:00:00 2001
+From: Philippe Coval 
+Date: Thu, 10 Nov 2016 12:47:39 +0100
+Subject: [PATCH 081/341] yocto: Add aarch64 for DragonBoard-410c
+
+Backported to 1.1-rel branch
+
+Change-Id: I0ebf93ca17a9a6624da3caaaf7487529b2c556d6
+Credit-to: Kotaro HASHIMOTO 
+Origin: 
https://lists.linuxfoundation.org/pipermail/automotive-discussions/2016-November/002805.html
+Signed-off-by: Philippe Coval 
+Reviewed-on: https://gerrit.iotivity.org/gerrit/14187
+Tested-by: jenkins-iotivity 
+Reviewed-by: Habib Virji 
+---
+ build_common/SConscript | 2 +-
+ resource/csdk/connectivity/build/SConscript | 2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/build_common/SConscript b/build_common/SConscript
+index 1427f08..56ea713 100644
+--- a/build_common/SConscript
 b/build_common/SConscript
+@@ -26,7 +26,7 @@ os_arch_map = {
+   'darwin': ['i386', 'x86_64'],
+   'ios': ['i386', 'x86_64', 'armv7', 'armv7s', 'arm64'],
+   'arduino': ['avr', 'arm'],
+-  'yocto': ['i586', 'i686', 'x86_64', 'arm', 'powerpc', 
'powerpc64', 'mips', 'mipsel'],
++  'yocto': ['i586', 'i686', 'x86_64', 'arm', 'aarch64', 
'powerpc', 'powerpc64', 'mips', 'mipsel'],
+   }
+ 
+ host = platform.system().lower()
+diff --git a/resource/csdk/connectivity/build/SConscript 
b/resource/csdk/connectivity/build/SConscript
+index b812fed..44c7d09 100644
+--- a/resource/csdk/connectivity/build/SConscript
 b/resource/csdk/connectivity/build/SConscript
+@@ -21,7 +21,7 @@ os_arch_map = {
+   'darwin': ['i386', 'x86_64'],
+   'ios': ['i386', 'x86_64', 'armv7', 'armv7s', 'arm64'],
+   'arduino': ['avr', 'arm'],
+-'yocto': ['i586', 'i686', 'x86_64', 'arm', 'powerpc', 
'powerpc64', 'mips', 'mipsel'],
++'yocto': ['i586', 'i686', 'x86_64', 'arm', 'aarch64', 
'powerpc', 'powerpc64', 'mips', 'mipsel'],
+   }
+ 
+ host = platform.system().lower()
+-- 
+1.9.1
+
diff --git a/recipes-core/iotivity/iotivity_1.2.0.bb 
b/recipes-core/iotivity/iotivity_1.2.0.bb
index dfae54b..60a2b56 100644
--- a/recipes-core/iotivity/iotivity_1.2.0.bb
+++ b/recipes-core/iotivity/iotivity_1.2.0.bb
@@ -10,6 +10,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE.md;md5=22bf216f3077c279aed7b36b1fa9e6d1"
 branch_iotivity = "1.2-rel"
 SRCREV = "1a2e71f9c470c7cc17157f83deb4488ee83050a4"
 SRC_URI = 
"git://github.com/iotivity/iotivity.git;destsuffix=${S};branch=${branch_iotivity};protocol=http;"
+SRC_URI += "file://0081-yocto-Add-aarch64-for-DragonBoard-410c.patch"
 
 url_tinycbor = "git://github.com/01org/tinycbor.git"
 SRCREV_tinycbor = "31c7f81d45d115d2007b1c881cbbd3a19618465c"
-- 
1.9.1

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

[yocto] [meta-oic][PATCH 2/3] doc: Translate README to ascii

2017-01-03 Thread Philippe Coval

(Cleanup UTF-8 chars)

Signed-off-by: Philippe Coval 
---
 README | 28 ++--
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/README b/README
index c6cf1a7..deba141 100644
--- a/README
+++ b/README
@@ -27,7 +27,7 @@ Recipes in meta-oic
 
 IoTivity packages built by the meta-oic layer
 =
-—- iotivity-resource : IoTivity resource libraries.
+-- iotivity-resource : IoTivity resource libraries.
 -- iotivity-resource-dev : IoTivity resource header files.
 -- iotivity-resource-thin-staticdev : IoTivity "thin" resource libraries.
 -- iotivity-resource-dbg : IoTivity resource libraries with debug
@@ -51,7 +51,7 @@ applications.
 -- iotivity-tests : IoTivity framework tests.
 -- iotivity-tests-dbg : Debug builds of IoTivity framework tests.
 -- iotivity : Meta-package for all IoTivity runtimes.
-—- iotivity-dev : Meta-package for all IoTivity runtimes and headers.
+-- iotivity-dev : Meta-package for all IoTivity runtimes and headers.
 -- iotivity-sensorboard : IoTivity SensorBoard application. (Sources
 located in iotivity-1.0.0/examples/OICSensorBoard)
 -- iotivity-simple-client: IoTivity resource simpleclient example.  
@@ -90,13 +90,13 @@ binary packages in the OS image.
 
 For eg., to include IoTivity resource and service samples and runtimes, use
 ...
-IMAGE_INSTALL_append += " iotivity-resource-samples iotivity-service-samples”
+IMAGE_INSTALL_append += " iotivity-resource-samples iotivity-service-samples"
 
 To include only IoTivity resource and service runtimes, use
 ...
-IMAGE_INSTALL_append += " iotivity”
+IMAGE_INSTALL_append += " iotivity"
 
-4. After initializing poky, run “bitbake ” to build the OS image, 
+4. After initializing poky, run "bitbake " to build the OS image, 
 and further deploy the image to your target.
 
 Building Yocto cross-toolchain with IoTivity for your target
@@ -105,26 +105,26 @@ Yocto has the capability to build cross-toolchains for 
targets
 to run on 32-bit and 64-bit machines.  
 Follow these steps to construct a toolchain for your target:
 
-1. You should’ve already completed the steps above to build IoTivity for your
+1. You should have already completed the steps above to build IoTivity for your
 target.
 
 2. Modify /conf/local.conf to install the IoTivity
-development packages to the toolchain’s sysroot. 
+development packages to the toolchain's sysroot. 
 ...
-IMAGE_INSTALL_append = " iotivity-dev”
+IMAGE_INSTALL_append = " iotivity-dev"
 
 To include only IoTivity "thin" resource headers and libraries, use
 ...
-IMAGE_INSTALL_append = " iotivity-resource-thin-staticdev”
+IMAGE_INSTALL_append = " iotivity-resource-thin-staticdev"
 
-3. After initializing poky, run “bitbake -c populate_sdk ” to build the
+3. After initializing poky, run "bitbake -c populate_sdk " to build the
 target platform SDK and toolchain. You may further install the toolchain
 on your build machine.
 
 Once installed, the toolchain may be used only after initialization. This is
-performed by an “environment setup script” at the root of the toolchain
+performed by an "environment setup script" at the root of the toolchain
 install location (usually in /opt/poky...). 
-To initialize, you must “source” this script into your shell environment. 
+To initialize, you must "source" this script into your shell environment. 
 
 Locations of IoTivity headers, runtimes and samples 
 ===
@@ -149,8 +149,8 @@ Building IoTivity applications for a Yocto target
 
 2. You can now use the Yocto toolchain for your target to cross-compile the
 application. As such, there is no standard procedure for this.  
-You may examine your toolchain’s environment setup script and accordingly
-modify your application’s build script to point to said tools.
+You may examine your toolchain's environment setup script and accordingly
+modify your application's build script to point to said tools.
 
 3. If you further want to package up your application in a Yocto software 
layer,
 you will have to write a BitBake recipe for it. Look inside
-- 
1.9.1

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

[yocto] [meta-oic][PATCH 3/3] Depends on glib-2.0-native to use gdbus-codegen

2017-01-03 Thread Philippe Coval

It was discovered while building AGL using Intel BSP.

Also fix dangling syslink,
 discovered while building ostro OS.

Signed-off-by: Philippe Coval 
---

Origin: https://github.com/TizenTeam/meta-oic/

 recipes-core/iotivity/iotivity_1.2.0.bb | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/recipes-core/iotivity/iotivity_1.2.0.bb 
b/recipes-core/iotivity/iotivity_1.2.0.bb
index 60a2b56..3e2b00e 100644
--- a/recipes-core/iotivity/iotivity_1.2.0.bb
+++ b/recipes-core/iotivity/iotivity_1.2.0.bb
@@ -1,7 +1,8 @@
+PR = "r1"
 SUMMARY = "IoTivity framework and SDK sponsored by the Open Connectivity 
Foundation."
 DESCRIPTION = "IoTivity is an open source software framework enabling seamless 
device-to-device connectivity to address the emerging needs of the Internet of 
Things."
 HOMEPAGE = "https://www.iotivity.org/";
-DEPENDS = "boost virtual/gettext chrpath-replacement-native expat openssl 
util-linux curl glib-2.0"
+DEPENDS = "boost virtual/gettext chrpath-replacement-native expat openssl 
util-linux curl glib-2.0 glib-2.0-native"
 EXTRANATIVEPATH += "chrpath-native"
 SECTION = "libs"
 LICENSE = "Apache-2.0"
@@ -380,7 +381,7 @@ do_install() {
 copy_file ${S}/iotivity.pc ${D}${libdir}/pkgconfig/
 ln -s iotivity/resource ${D}${includedir}/resource
 ln -s iotivity/service ${D}${includedir}/service
-ln -s ../iotivity/resource/oc_logger/targets ${D}${includedir}/resource/
+ln -s oc_logger/targets ${D}${includedir}/resource/
 
 chrpath -d ${D}${libdir}/*.so
 }
-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-rt

2017-01-03 Thread Trevor Woerner

This patchset adds a new recipe to meta-raspberrypi to give users the option
to choose a full PREEMPT_RT Linux kernel with the full PREEMPT_RT patch
applied. It is based on the linux-raspberrypi 4.4 kernel with the -rt patch
from https://www.kernel.org/pub/linux/kernel/projects/rt/, specifically it is
linux-raspberrypi-4.4.35 with the patch-4.4.32-rt43 -rt patch applied.

To select this kernel for your image, set:

PREFERRED_PROVIDER_virtual/kernel = "linux-raspberrypi-rt"

in local.conf or similar.

Normally when using the -rt kernel on the raspberrypi and enabling full
preemption (CONFIG_PREEMPT_RT_FULL=y), the device will become unstable and
be prone to frequent crashing. There are two ways to fix this problem:
1) disable FIQ
2) patch the FIQ handling to avoid the race which causes the crashes

The FIQ can be disabled by appending "dwc_otg.fiq_enable=0
dwc_otg.fiq_fsm_enable=0" to the kernel cmdline. Disabling the FIQ altogether
does fix the problem but increases latencies. The better solution is to patch
the FIQ handling code to avoid the race condition that causes the crash. This
allows the FIQ to be used, and lowers latencies.

This patch implements the 2nd option of patching the kernel code to avoid the
race condition. Thus providing a better -rt experience on this platform.

A full explanation of this issue can be found here:

https://www.osadl.org/Single-View.111+M5c03315dc57.0.html

This kernel recipe ignores the raspberrypi-specific kernel configuration
mechanisms of the other raspberrypi kernel recipes so that users are free to
modify the base kernel configuration using fragments in the usual Yocto way.
The base defconfig for this kernel is the same as the linux-raspberrypi-4.4
kernel but with full preemption enabled (and whatever else that pulls in).

Trevor Woerner (1):
  linux-raspberrypi-rt: add

 .../0001-fix-dtbo-rules.patch  |44 +
 .../FIQ_PREEMPT_RT_on_raspi.patch  |   310 +
 .../linux/linux-raspberrypi-rt-4.4/defconfig   |  5419 
 .../patch-4.4.32-rt43.patch| 31403 +++
 recipes-kernel/linux/linux-raspberrypi-rt_4.4.bb   |55 +
 5 files changed, 37231 insertions(+)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-rt-4.4/0001-fix-dtbo-rules.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-rt-4.4/FIQ_PREEMPT_RT_on_raspi.patch
 create mode 100644 recipes-kernel/linux/linux-raspberrypi-rt-4.4/defconfig
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi-rt-4.4/patch-4.4.32-rt43.patch
 create mode 100644 recipes-kernel/linux/linux-raspberrypi-rt_4.4.bb

-- 
2.10.2

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

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-rt: add

2017-01-03 Thread Andreas Müller

On Tue, Jan 3, 2017 at 8:38 PM, Trevor Woerner  wrote:
> Add an -rt kernel option for Raspberry Pi that includes the FIQ patch which
> adds stability to the -rt kernel (with full preemption enabled) and is an
> improvement to simply disabling FIQ on the kernel cmdline.
>
> Signed-off-by: Trevor Woerner 
I played around with rt-kernel too but had no solution for the crashes
so far. Will test soon and hope you are my hero..

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

Re: [yocto] [OE-core] OpenEmbedded Stand at FOSDEM

2017-01-03 Thread Andreas Müller

On Tue, Jan 3, 2017 at 4:32 PM, Philip Balister  wrote:
> Every year since 2007, OpenEmbedded has a stand at FOSDEM
> (http://www.fosdem.org)
>
> From the first year:
>
> https://www.flickr.com/photos/32615155@N00/405229708/in/album-72157594561002629/
>
> Belen and I are sort of organizing this, but both of us are also
> involved in devrooms, so we will need a lot of help manning the stand
> and getting some demos together.
>
> Demos should try and show how the project makes embedded work easier, by
> showing tools and/or cool examples of devices using Linux built with
> OpenEmbedded. In previous years, we've shown toaster with data collected
> from demos on the table. Collections of devices running images built
> from the same recipe and interesting products using Linux by OpenEmbedded.
>
> I'm happy to try and organize demos and staffing, but I could really use
> some help this year, so if you are in a position to tak ethe lead on
> operating the stand, that would be a huge help to me and the rest of the
> project.
>
> Thanks,
>
> Philip
> --
I could bring along

1. Raspi2 + Hifiberry + Speakers + Midi-Keyboard + Xbox-controller
2. a SDCard full of desktops/multimedia/office/games using 1.
3. 2 days time
4. ?? - let me know

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

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-rt: add

2017-01-03 Thread Andreas Müller

On Wed, Jan 4, 2017 at 1:05 AM, Andreas Müller
 wrote:
> On Tue, Jan 3, 2017 at 8:38 PM, Trevor Woerner  wrote:
>> Add an -rt kernel option for Raspberry Pi that includes the FIQ patch which
>> adds stability to the -rt kernel (with full preemption enabled) and is an
>> improvement to simply disabling FIQ on the kernel cmdline.
>>
>> Signed-off-by: Trevor Woerner 
> I played around with rt-kernel too but had no solution for the crashes
> so far. Will test soon and hope you are my hero..
>
Have a rt-kernel on raspi without crashes. FIQ patch is it: Thanks so
much for sorting this out!

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

[yocto] OpenEmbedded Stand at FOSDEM

[yocto] Yocto Project Status WW01

[yocto] Yocto Project Status WW01

[yocto] [opkg-utils PATCH] Added support to generate index file with multiple version per package

Re: [yocto] [opkg-devel] [opkg-utils PATCH] Added support to generate index file with multiple version per package

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Jan. 3, 2017 8:00 AM US Pacific Time

Re: [yocto] [OE-core] Yocto Project Status WW01

[yocto] [meta-oic][PATCH 1/3] meta-oic: Hotfix to support aarch64 for DragonBoard-410c

[yocto] [meta-oic][PATCH 2/3] doc: Translate README to ascii

[yocto] [meta-oic][PATCH 3/3] Depends on glib-2.0-native to use gdbus-codegen

[yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-rt

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-rt: add

Re: [yocto] [OE-core] OpenEmbedded Stand at FOSDEM

Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-rt: add

14 matches

Site Navigation

Mail list logo

Footer information