[yocto] [layerindex-web] [PATCH] update.py: update actual branch for layer and bitbake

2017-05-16 Thread Robert Yang 
Add an option "-a" to update actual branch for layer and bitbake, it is
useful when there are many layers and need update actual branches
frequantly. We only can update them via website without this patch,
which is not funny and easy to make mistakes.

Signed-off-by: Robert Yang 
---
 layerindex/update.py | 54 
 1 file changed, 54 insertions(+)

diff --git a/layerindex/update.py b/layerindex/update.py
index d5c56cd..aa2fb38 100755
--- a/layerindex/update.py
+++ b/layerindex/update.py
@@ -85,6 +85,51 @@ def prepare_update_layer_command(options, branch, layer, 
updatedeps=False):
 cmd += ' -q'
 return cmd
 
+def get_actual_branch_format():
+return "::"
+
+def update_actual_branches(options):
+"""Update actual branch for layers and bitbake in database"""
+to_save = set()
+for opt in options.actual_branches.split(','):
+opt_list = opt.split(':')
+if len(opt_list) != 3:
+logger.error("Bad format: %s, use %s" % (opt, 
get_actual_branch_format()))
+sys.exit(1)
+layer_name = opt_list[0]
+branch = opt_list[1]
+actual_branch_new = opt_list[2]
+if not (layer_name and branch and actual_branch_new):
+logger.error("Bad format: %s, one of %s is null" % (opt, 
get_actual_branch_new_format()))
+sys.exit(1)
+
+if layer_name == 'bitbake':
+branchobj = utils.get_branch(branch)
+if actual_branch_new != branchobj.bitbake_branch:
+logger.info("bitbake: %s.bitbake_branch: %s -> %s" % (branch, 
branchobj.bitbake_branch, actual_branch_new))
+branchobj.bitbake_branch = actual_branch_new
+to_save.add(branchobj)
+else:
+logger.warn("bitbake: %s.bitbake_branch is already %s, so no 
change" % (branch, actual_branch_new))
+else:
+layer = utils.get_layer(layer_name)
+if not layer:
+logger.error("Layer name '%s' not found in database" % 
layer_name)
+sys.exit(1)
+layerbranch = layer.get_layerbranch(branch)
+if not layerbranch:
+logger.error("Branch '%s' not found in database" % branch)
+sys.exit(1)
+if actual_branch_new != layerbranch.actual_branch:
+logger.info("%s: %s.actual_branch: %s -> %s" % (layer_name, 
branch, layerbranch.actual_branch, actual_branch_new))
+layerbranch.actual_branch = actual_branch_new
+to_save.add(layerbranch)
+else:
+logger.warn("%s: %s.actual_branch is already %s, so no change" 
% (layer_name, branch, actual_branch_new))
+
+# At last, do the save
+for s in to_save:
+s.save()
 
 def main():
 if LooseVersion(git.__version__) < '0.3.1':
@@ -102,6 +147,11 @@ def main():
 parser.add_option("-l", "--layer",
 help = "Specify layers to update (use commas to separate 
multiple). Default is all published layers.",
 action="store", dest="layers")
+parser.add_option("-a", "--actual-branch",
+help = "Update actual branch for layer and bitbake, \
+the format is: %s (use commas to separate multiple), \
+use 'bitbake' as  to update bitbake branch" % 
get_actual_branch_format(),
+action="store", dest="actual_branches", default='')
 parser.add_option("-r", "--reload",
 help = "Reload recipe data instead of updating since last update",
 action="store_true", dest="reload")
@@ -187,6 +237,10 @@ def main():
 logger.error("Layer index lock timeout expired")
 sys.exit(1)
 try:
+if options.actual_branches:
+update_actual_branches(options)
+return
+
 bitbakepath = os.path.join(fetchdir, 'bitbake')
 
 if not options.nofetch:
-- 
2.10.2

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

Re: [yocto] [meta-raspberrypi] rpi0-w wifi&bluetooth problem

2017-05-16 Thread Andrei Gherzan 
Hello,

On Tue, May 16, 2017 at 5:34 AM, 김재환  wrote:

> Hi.
>
>
>
> i build core-image-minimal for rpi0-w.
>
> it works nicely but not working wlan0 and bluetooth.
>
>
>
> so i tried this post
> .
> but still not working.
>
>
>
> the error was
>
> $ifup wlan0
>
> Successfully initialized wpa_supplicant
>
> rfkill: cannot get wiphy information
>
> Could not read interface wlan0 flags: No such device
>
> WEXT: could not set interface 'wlan0' UP
>
> wlan0: Failed to initialize driver interface
>
> ifconfig: SIOCGIFFLAGS No such device
>
>
>
> anybody solve this problem?
>

Can you pastebin a dmesg log, please? I want to confirm that my theory is
correct.

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

Re: [yocto] [meta-raspberrypi] Pyro branch

2017-05-16 Thread Andrei Gherzan 
On Mon, May 15, 2017 at 10:14 AM, Paul Barker  wrote:
> Hi all,
>
> Yocto Project 2.3 has now been released so I think it's time to create
> a pyro branch for meta-raspberrypi.
>

I'm setting up today mirroring jobs in jenkins so we can only work in
github and all the other repos will get updated automatically. As well
I'll merge whatever is left in github and start a branch as soon as I
finish with this.

> I've briefly discussed stable branch maintainership with Andrei and
> I'd like to volunteer as maintainer of the pyro branch. That should
> spread the workload out a little bit. Does anyone have any thoughts or
> objections to that?

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

Re: [yocto] [meta-selinux][PATCH] systemd: no need to inherit enable-selinux

2017-05-16 Thread Joe MacDonald 
[RE: [yocto] [meta-selinux][PATCH] systemd: no need to inherit enable-selinux] 
On 17.05.08 (Mon 01:40) Huang, Jie (Jackie) wrote:

> 
> 
> > -Original Message-
> > From: Joe MacDonald [mailto:joe_macdon...@mentor.com]
> > Sent: Tuesday, May 02, 2017 21:14
> > To: Huang, Jie (Jackie)
> > Cc: yocto@yoctoproject.org
> > Subject: Re: [yocto] [meta-selinux][PATCH] systemd: no need to inherit 
> > enable-
> > selinux
> > 
> > [[yocto] [meta-selinux][PATCH] systemd: no need to inherit enable-selinux] 
> > On
> > 17.02.22 (Wed 14:44) jackie.hu...@windriver.com wrote:
> > 
> > > From: Jackie Huang 
> > >
> > > The selinux PACKAGECONFIG is properly handled in
> > > the recipe in oe-core, no need to inherit the
> > > enable-selinux bbclass.
> > 
> > That might be true, but other than belt-and-suspenders, what's the
> > harm in this being in the recipe?  I don't necessarily think it's an
> > invalid change but my quick count shows ~44 instances of 'inherit
> > enable-selinux' and 'inherit with-selinux' in meta-selinux, why's this
> > one significant?
> 
> That's because I have a patch to change the PACKAGECONFIG for selinux
> in oe-core to fix a dependency issue:
> 
> -PACKAGECONFIG[selinux] = "--enable-selinux,--disable-selinux,libselinux"
> +PACKAGECONFIG[selinux] = 
> "--enable-selinux,--disable-selinux,libselinux,initscripts-sushell"
> 
> But it would be overrode by the one in enable-selinux.bbclass:
> $ grep PACKAGECONFIG enable-selinux.bbclass
> PACKAGECONFIG_append = " ${@target_selinux(d)}"
> PACKAGECONFIG[selinux] = "--enable-selinux,--disable-selinux,libselinux,"
> 
> So I need to remove the inherit here in meta-selinux.

Sorry, this fell between the cracks.

So, let me make sure I understand what you're saying.  This oe-core
commit:

commit 1881c5e0c426a193630e5eed5b629b69ff3741d5
Author: Kai Kang 
Date:   Wed Jul 8 14:26:01 2015 +0800

systemd: add PACKAGECONFIG selinux

Add PACKAGECONFIG 'selinux' for systemd. debug-shell.service starts
different shell according whether selinux is enabled.

(From OE-Core rev: 3d1aa27191fe4c21428eaf4ae036acb1496b7df7)

Signed-off-by: Kai Kang 
Signed-off-by: Richard Purdie 

conflicts with the --enable/--disable settings in meta-selinux and  you
want to remove the setting in meta-selinux?  Again, I don't specifically
object to this, but I'd like to understand the why of it.  Is there a
valid scenario to include meta-selinux in your project but have selinux
disabled?  If so, I would think the settings in meta-selinux should
still take precedence.  Otherwise, I'm confused why the other 40-ish
cases aren't also covered.  I haven't investigated, but are all the
others in non-oe-core layers, maybe?

Thanks,
-J.

> 
> Thanks,
> Jackie
> 
> > 
> > -J.
> > 
> > >
> > > Signed-off-by: Jackie Huang 
> > > ---
> > >  recipes-core/systemd/systemd_%.bbappend | 1 -
> > >  1 file changed, 1 deletion(-)
> > >
> > > diff --git a/recipes-core/systemd/systemd_%.bbappend b/recipes-
> > core/systemd/systemd_%.bbappend
> > > index 8d9029b..f1bdaf8 100644
> > > --- a/recipes-core/systemd/systemd_%.bbappend
> > > +++ b/recipes-core/systemd/systemd_%.bbappend
> > > @@ -1,2 +1 @@
> > >  inherit enable-audit
> > > -inherit enable-selinux
> > > --
> > > 2.8.3
> > >
> > --
> > -Joe MacDonald.
> > :wq

-- 
-Joe MacDonald.
:wq


signature.asc
Description: Digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-rockchip] [PATCH v3 0/3] Add video codec recipes

2017-05-16 Thread ayaka 
Those packages are the userspace libraries for the Rockchip
Android video codec driver.

Also a minimal image used for verified the media framework is included.

ayaka (3):
  recipes-multimedia: add Rockchip MPP library
  recipes-multimedia: add gstreamer rockchip support
  recipes-multimedia: images: rockchip media image

 .../gstreamer/gstreamer1.0-rockchip.inc| 32 ++
 .../gstreamer/gstreamer1.0-rockchip_20170516.bb|  9 ++
 .../gstreamer/gstreamer1.0-rockchip_git.bb | 13 +
 recipes-multimedia/images/rockchip-media-image.bb  | 21 ++
 recipes-multimedia/rockchip-mpp/rockchip-mpp.inc   | 21 ++
 .../rockchip-mpp/rockchip-mpp_20170412.bb  |  9 ++
 .../rockchip-mpp/rockchip-mpp_git.bb   | 16 +++
 7 files changed, 121 insertions(+)
 create mode 100644 recipes-multimedia/gstreamer/gstreamer1.0-rockchip.inc
 create mode 100644 
recipes-multimedia/gstreamer/gstreamer1.0-rockchip_20170516.bb
 create mode 100644 recipes-multimedia/gstreamer/gstreamer1.0-rockchip_git.bb
 create mode 100644 recipes-multimedia/images/rockchip-media-image.bb
 create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp.inc
 create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp_20170412.bb
 create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp_git.bb

-- 
2.9.4

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

[yocto] [PATCH v3 1/3] recipes-multimedia: add Rockchip MPP library

2017-05-16 Thread ayaka 
MPP means Media Process Platform. The MPP is a middleware
for the other video encoder/decoder interface, translating
the video information into the hardware registers.

Signed-off-by: ayaka 
---
 recipes-multimedia/rockchip-mpp/rockchip-mpp.inc| 21 +
 .../rockchip-mpp/rockchip-mpp_20170412.bb   |  9 +
 recipes-multimedia/rockchip-mpp/rockchip-mpp_git.bb | 16 
 3 files changed, 46 insertions(+)
 create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp.inc
 create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp_20170412.bb
 create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp_git.bb

diff --git a/recipes-multimedia/rockchip-mpp/rockchip-mpp.inc 
b/recipes-multimedia/rockchip-mpp/rockchip-mpp.inc
new file mode 100644
index 000..6a45637
--- /dev/null
+++ b/recipes-multimedia/rockchip-mpp/rockchip-mpp.inc
@@ -0,0 +1,21 @@
+# Copyright (C) 2016 - 2017 Randy Li 
+# Released under the GNU GENERAL PUBLIC LICENSE Version 2
+# (see COPYING.GPLv2 for the terms)
+
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = 
"file://inc/rk_mpi.h;beginline=4;endline=14;md5=acbba394ae5639b0c786f60c1f48e3d6"
+
+inherit pkgconfig cmake
+
+EXTRA_OECMAKE = " \
+-DRKPLATFORM=ON   \
+-DHAVE_DRM=ON \
+"
+
+PACKAGES = "${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN} rockchip-vpu"
+FILES_rockchip-vpu = "${libdir}/lib*vpu${SOLIBS}"
+FILES_${PN} = "${libdir}/lib*mpp${SOLIBS}"
+FILES_${PN}-dev = "${libdir}/lib*${SOLIBSDEV} ${includedir} 
${libdir}/pkgconfig"
+SECTION_${PN}-dev = "devel"
+FILES_${PN}-staticdev = "${libdir}/*.a"
+SECTION_${PN}-staticdev = "devel"
diff --git a/recipes-multimedia/rockchip-mpp/rockchip-mpp_20170412.bb 
b/recipes-multimedia/rockchip-mpp/rockchip-mpp_20170412.bb
new file mode 100644
index 000..501306a
--- /dev/null
+++ b/recipes-multimedia/rockchip-mpp/rockchip-mpp_20170412.bb
@@ -0,0 +1,9 @@
+# Copyright (C) 2016 - 2017 Randy Li 
+# Released under the GNU GENERAL PUBLIC LICENSE Version 2
+# (see COPYING.GPLv2 for the terms)
+include rockchip-mpp.inc
+
+TAG = "release_${PV}"
+SRC_URI = "git://github.com/rockchip-linux/mpp.git;tag=${TAG};nobranch=1"
+
+S = "${WORKDIR}/git"
diff --git a/recipes-multimedia/rockchip-mpp/rockchip-mpp_git.bb 
b/recipes-multimedia/rockchip-mpp/rockchip-mpp_git.bb
new file mode 100644
index 000..23f3f15
--- /dev/null
+++ b/recipes-multimedia/rockchip-mpp/rockchip-mpp_git.bb
@@ -0,0 +1,16 @@
+# Copyright (C) 2016 - 2017 Randy Li 
+# Released under the GNU GENERAL PUBLIC LICENSE Version 2
+# (see COPYING.GPLv2 for the terms)
+
+DEFAULT_PREFERENCE = "-1"
+
+include rockchip-mpp.inc
+DEPENDS = "git-replacement-native"
+
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+FILESPATH_prepend := "${THISDIR}/${PN}:"
+
+SRCREV = "${AUTOREV}"
+SRC_URI = "git://github.com/rockchip-linux/mpp.git;branch=develop"
+
+S = "${WORKDIR}/git"
-- 
2.9.4

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

[yocto] [PATCH v3 2/3] recipes-multimedia: add gstreamer rockchip support

2017-05-16 Thread ayaka 
This Gstreamer plugin provides a encoder and decoder plugin
for Gstreamer through the Rockchip MPP library.

Signed-off-by: ayaka 
---
 .../gstreamer/gstreamer1.0-rockchip.inc| 32 ++
 .../gstreamer/gstreamer1.0-rockchip_20170516.bb|  9 ++
 .../gstreamer/gstreamer1.0-rockchip_git.bb | 13 +
 3 files changed, 54 insertions(+)
 create mode 100644 recipes-multimedia/gstreamer/gstreamer1.0-rockchip.inc
 create mode 100644 
recipes-multimedia/gstreamer/gstreamer1.0-rockchip_20170516.bb
 create mode 100644 recipes-multimedia/gstreamer/gstreamer1.0-rockchip_git.bb

diff --git a/recipes-multimedia/gstreamer/gstreamer1.0-rockchip.inc 
b/recipes-multimedia/gstreamer/gstreamer1.0-rockchip.inc
new file mode 100644
index 000..fd8fc98
--- /dev/null
+++ b/recipes-multimedia/gstreamer/gstreamer1.0-rockchip.inc
@@ -0,0 +1,32 @@
+# Copyright (C) 2016 - 2017 Randy Li 
+# Released under the GNU GENERAL PUBLIC LICENSE Version 2
+# (see COPYING.GPLv2 for the terms)
+
+require recipes-multimedia/gstreamer/gstreamer1.0-plugins.inc
+
+DESCRIPTION = "GStreamer 1.0 plugins for Rockchip platforms"
+
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM = "file://COPYING;md5=6d1e4aa87f6192354d3de840cf774d93"
+DEPENDS += "gstreamer1.0-plugins-base"
+
+inherit gettext autotools pkgconfig
+
+PACKAGECONFIG ??= " \
+mpp \
+"
+PACKAGECONFIG[mpp]= 
"--enable-rockchipmpp,--disable-rockchipmpp,rockchip-mpp"
+PACKAGECONFIG[vpudec] = "--enable-vpudec,--disable-vpudec,rockchip-vpu"
+PACKAGECONFIG[drm]= 
"--enable-drmrockchip,--disable-drmrockchip,libdrm-rockchip"
+
+EXTRA_OECONF += "\
+--disable-kms\
+"
+EXTRA_OECONF_remove = "--disable-gtk-doc"
+
+do_configure[prefuncs] = " delete_pkg_m4_file"
+
+do_configure() {
+NOCONFIGURE=true ${S}/autogen.sh
+oe_runconf
+}
diff --git a/recipes-multimedia/gstreamer/gstreamer1.0-rockchip_20170516.bb 
b/recipes-multimedia/gstreamer/gstreamer1.0-rockchip_20170516.bb
new file mode 100644
index 000..e3fecaf
--- /dev/null
+++ b/recipes-multimedia/gstreamer/gstreamer1.0-rockchip_20170516.bb
@@ -0,0 +1,9 @@
+# Copyright (C) 2016 - 2017 Randy Li 
+# Released under the GNU GENERAL PUBLIC LICENSE Version 2
+# (see COPYING.GPLv2 for the terms)
+include gstreamer1.0-rockchip.inc
+
+TAG = "release_${PV}"
+SRC_URI = 
"git://github.com/rockchip-linux/gstreamer-rockchip.git;tag=${TAG};nobranch=1"
+
+S = "${WORKDIR}/git"
diff --git a/recipes-multimedia/gstreamer/gstreamer1.0-rockchip_git.bb 
b/recipes-multimedia/gstreamer/gstreamer1.0-rockchip_git.bb
new file mode 100644
index 000..bd20121
--- /dev/null
+++ b/recipes-multimedia/gstreamer/gstreamer1.0-rockchip_git.bb
@@ -0,0 +1,13 @@
+# Copyright (C) 2016 - 2017 Randy Li 
+# Released under the GNU GENERAL PUBLIC LICENSE Version 2
+# (see COPYING.GPLv2 for the terms)
+
+DEFAULT_PREFERENCE = "-1"
+
+include gstreamer1.0-rockchip.inc
+
+SRCBRANCH ?= "develop"
+SRCREV = "${AUTOREV}"
+SRC_URI = 
"git://github.com/rockchip-linux/gstreamer-rockchip.git;branch=develop"
+
+S = "${WORKDIR}/git"
-- 
2.9.4

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

[yocto] [PATCH v3 3/3] recipes-multimedia: images: rockchip media image

2017-05-16 Thread ayaka 
A image for debugging the hardware video encoder/decoder.
I also use this image for developing the Gstreamer.

Signed-off-by: ayaka 
---
 recipes-multimedia/images/rockchip-media-image.bb | 21 +
 1 file changed, 21 insertions(+)
 create mode 100644 recipes-multimedia/images/rockchip-media-image.bb

diff --git a/recipes-multimedia/images/rockchip-media-image.bb 
b/recipes-multimedia/images/rockchip-media-image.bb
new file mode 100644
index 000..ea993c1
--- /dev/null
+++ b/recipes-multimedia/images/rockchip-media-image.bb
@@ -0,0 +1,21 @@
+# Copyright (C) 2017 Randy Li 
+# Released under the MIT license (see COPYING.MIT for the terms)
+
+include recipes-core/images/core-image-minimal.bb
+
+LICENSE = "MIT"
+DESCRIPTION = "Multimedia image for Rockchip devices."
+
+IMAGE_FEATURES_append = " package-management ssh-server-dropbear"
+IMAGE_INSTALL_append = " gdbserver gstreamer1.0-rockchip  \
+ gstreamer1.0-meta-base gstreamer1.0-meta-video gstreamer1.0-meta-audio \
+ gstreamer1.0-plugins-good-isomp4 gstreamer1.0-plugins-good-multifile \
+ gstreamer1.0-plugins-good-imagefreeze \
+ gstreamer1.0-plugins-bad-autoconvert  gstreamer1.0-plugins-bad-camerabin2 \
+ gstreamer1.0-plugins-bad-kmssink gstreamer1.0-plugins-bad-rawparse \
+ gstreamer1.0-plugins-bad-videoparsersbad \
+ gstreamer1.0-plugins-bad-mpegtsdemux \
+ gstreamer1.0-meta-debug \
+"
+
+TOOLCHAIN_HOST_TASK += "nativesdk-cmake"
-- 
2.9.4

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

Re: [yocto] [meta-rockchip] [PATCH v3 0/3] Add video codec recipes

2017-05-16 Thread Khem Raj 
On Tue, May 16, 2017 at 7:18 AM, ayaka  wrote:
> Those packages are the userspace libraries for the Rockchip
> Android video codec driver.
>
> Also a minimal image used for verified the media framework is included.
>

some recipes are pinned with GPL-2.0 and some with other licenses. Usually
metadata is better under MIT, is it intentional ? if not then it would
be good to follow consistent license for metadata

> ayaka (3):
>   recipes-multimedia: add Rockchip MPP library
>   recipes-multimedia: add gstreamer rockchip support
>   recipes-multimedia: images: rockchip media image
>
>  .../gstreamer/gstreamer1.0-rockchip.inc| 32 
> ++
>  .../gstreamer/gstreamer1.0-rockchip_20170516.bb|  9 ++
>  .../gstreamer/gstreamer1.0-rockchip_git.bb | 13 +
>  recipes-multimedia/images/rockchip-media-image.bb  | 21 ++
>  recipes-multimedia/rockchip-mpp/rockchip-mpp.inc   | 21 ++
>  .../rockchip-mpp/rockchip-mpp_20170412.bb  |  9 ++
>  .../rockchip-mpp/rockchip-mpp_git.bb   | 16 +++
>  7 files changed, 121 insertions(+)
>  create mode 100644 recipes-multimedia/gstreamer/gstreamer1.0-rockchip.inc
>  create mode 100644 
> recipes-multimedia/gstreamer/gstreamer1.0-rockchip_20170516.bb
>  create mode 100644 recipes-multimedia/gstreamer/gstreamer1.0-rockchip_git.bb
>  create mode 100644 recipes-multimedia/images/rockchip-media-image.bb
>  create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp.inc
>  create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp_20170412.bb
>  create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp_git.bb
>
> --
> 2.9.4
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-rockchip] [PATCH v3 0/3] Add video codec recipes

2017-05-16 Thread ayaka 



On 05/16/2017 10:24 PM, Khem Raj wrote:

On Tue, May 16, 2017 at 7:18 AM, ayaka  wrote:

Those packages are the userspace libraries for the Rockchip
Android video codec driver.

Also a minimal image used for verified the media framework is included.


some recipes are pinned with GPL-2.0 and some with other licenses. Usually
metadata is better under MIT, is it intentional ? if not then it would

Yes. I want to keep it from secret as much as possible.

be good to follow consistent license for metadata


ayaka (3):
   recipes-multimedia: add Rockchip MPP library
   recipes-multimedia: add gstreamer rockchip support
   recipes-multimedia: images: rockchip media image

  .../gstreamer/gstreamer1.0-rockchip.inc| 32 ++
  .../gstreamer/gstreamer1.0-rockchip_20170516.bb|  9 ++
  .../gstreamer/gstreamer1.0-rockchip_git.bb | 13 +
  recipes-multimedia/images/rockchip-media-image.bb  | 21 ++
  recipes-multimedia/rockchip-mpp/rockchip-mpp.inc   | 21 ++
  .../rockchip-mpp/rockchip-mpp_20170412.bb  |  9 ++
  .../rockchip-mpp/rockchip-mpp_git.bb   | 16 +++
  7 files changed, 121 insertions(+)
  create mode 100644 recipes-multimedia/gstreamer/gstreamer1.0-rockchip.inc
  create mode 100644 
recipes-multimedia/gstreamer/gstreamer1.0-rockchip_20170516.bb
  create mode 100644 recipes-multimedia/gstreamer/gstreamer1.0-rockchip_git.bb
  create mode 100644 recipes-multimedia/images/rockchip-media-image.bb
  create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp.inc
  create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp_20170412.bb
  create mode 100644 recipes-multimedia/rockchip-mpp/rockchip-mpp_git.bb

--
2.9.4



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

Re: [yocto] [PATCH v3 1/3] recipes-multimedia: add Rockchip MPP library

2017-05-16 Thread Trevor Woerner 
Randy,

Neither of the issues that were identified in your v2 of this patch were
addressed in this v3. Namely:

1) please use your real name (first, last) in your signed-off-by line
2) please don't create a package from this recipe whose name doesn't include
   the recipe name (i.e. please don't create "rockchip-vpu" from a recipe
   "rockchip-mpp"), suggestions were provided

Aside from the email headers and the version of git used, this patch is
identical to the v2 you submitted.

Best regards,
Trevor
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [qa-tools][PATCH] Full-test-cycle-wrapper: Add support for point releases

2017-05-16 Thread jose . perez . carranza 
From: Jose Perez Carranza 

Add support to scenarios were a execution is needed for branch different
from master, delete lsb-joule environment as is not supported and add
logic to do the “Testopia connection” modular and reusable by other
scripts.

Signed-off-by: Jose Perez Carranza 
---
 scripts/full-test-cycle-wrapper.sh | 16 +++---
 testopia_update.py | 44 --
 2 files changed, 41 insertions(+), 19 deletions(-)

diff --git a/scripts/full-test-cycle-wrapper.sh 
b/scripts/full-test-cycle-wrapper.sh
index 2b3a130..7dcd62e 100755
--- a/scripts/full-test-cycle-wrapper.sh
+++ b/scripts/full-test-cycle-wrapper.sh
@@ -51,6 +51,13 @@ create_test_run(){
   OPT="-o $2"
fi
 
+#If point release is used then milestone is not asigned
+   if [[ $MILESTONE == M* ]]; then
+  BUILD_MILESTONE="$VERSION $MILESTONE"
+   else
+  BUILD_MILESTONE="$VERSION$MILESTONE"
+   fi
+
#echo " CREATING TEST RUNS FOR - $1 - #"
for ENV in "${ENVIRONMENTS[@]}"
do
@@ -61,7 +68,7 @@ create_test_run(){
  do
 #call the script that creates Test Runs
 ./testopia_update.py --config $CONFIG_FILE -a $ACTION -p "${1}" -c 
$EXTP -b $BRANCH \
--e "$ENV"  --project-version $VERSION --project-milestone "$VERSION 
$MILESTONE" \
+-e "$ENV"  --project-version $VERSION --project-milestone 
"$BUILD_MILESTONE" \
 --project-date $PJDATE --project-revision $RELEASE-$REVISION $OPT 
$TEST_PLAN --verbose
  done
done
@@ -119,7 +126,7 @@ create_meta-intel(){
create_test_run "${1}" "core-image-sato-sdk_ANYBSP"
 
#BSP Autos LSB
-   ENVIRONMENTS=("core2-32_lsb_MMAX32" "corei7-64_lsb_NUC" 
"corei7-64_lsb_MMAX64" "corei7-64_lsb_Joule" "corei7-64_lsb_CherryHill")
+   ENVIRONMENTS=("core2-32_lsb_MMAX32" "corei7-64_lsb_NUC" 
"corei7-64_lsb_MMAX64" "corei7-64_lsb_CherryHill")
 
EXECUTION_TYPE="AUTO"
create_test_run "${1}" "core-image-lsb-sdk_ANYBSP"
@@ -226,7 +233,9 @@ usage(){
   echo " -p PROJECT VERSION  {2.2 2.3 2.4}
   Version of the project."
   echo " -m PROJECT MILESTONE {M1 M2 M3 M4}
-  Milestone of the project."
+  Milestone of the project.
+ if is point release set milestone with .#
+ .1 .2 .3"
   echo " -r RELEASE COMMIT {XX}
   SCM Revision of the project, commit of branch 
tested."
   echo " -c RELEAE CANDIDATE {rc1 rc2 rcX}
@@ -236,6 +245,7 @@ usage(){
   exit
 }
 
+
 if [[ ( $# == "--help") ||  $# == "-h" || $# -eq 0 ]] ; then
 usage
 exit 0
diff --git a/testopia_update.py b/testopia_update.py
index 50c3325..0a3f7f5 100755
--- a/testopia_update.py
+++ b/testopia_update.py
@@ -14,7 +14,7 @@ DEFAULT_CONFIG_FILE = "testopia_update.config"
 DEFAULT_STORE_LOCATION = "/tmp/testopia_update"
 
 ACTIONS = ('create', 'update')
-BRANCHES = ('master', 'jethro', 'dizzy', 'daisy', 'noexists')
+BRANCHES = ('master', 'jethro', 'dizzy', 'daisy', 'noexists', "pyro")
 CATEGORIES = ('AUTO', 'MANUAL')
 
 
@@ -54,6 +54,31 @@ def load_opts(args, opts_list, opts):
 'and --results-log if test run was already 
created')
 sys.exit(1)
 
+
+def connect_to_testopia():
+config = None
+opts = Options()
+
+testopia_config = ['url', 'username', 'password', 'store_location']
+
+if not args.config and os.path.exists(DEFAULT_CONFIG_FILE):
+args.config = DEFAULT_CONFIG_FILE
+
+if args.config:
+config = ConfigParser.SafeConfigParser()
+config.read(args.config)
+
+for to in testopia_config:
+setattr(opts, to, config.get("Testopia", to))
+
+load_opts(args, testopia_config, opts)
+
+if not os.path.exists(opts.store_location):
+os.makedirs(opts.store_location)
+
+return opts, config
+
+
 class Options(object):
 pass
 
@@ -132,25 +157,12 @@ if __name__ == '__main__':
 'project_version', 'project_milestone', 'project_revision',
 'project_date']
 
-config = None
-if not args.config and os.path.exists(DEFAULT_CONFIG_FILE):
-args.config = DEFAULT_CONFIG_FILE
-
-if args.config:
-config = ConfigParser.SafeConfigParser()
-config.read(args.config)
-
-for to in testopia_config:
-setattr(opts, to, config.get("Testopia", to))
-load_opts(args, testopia_config, opts)
-
-if not os.path.exists(opts.store_location):
-os.makedirs(opts.store_location)
-
 kwargs = {}
 if args.plan_name:
 kwargs['plan_name'] = args.plan_name
 
+opts, config = connect_to_testopia()
+
 testopia = Testopia(opts.username, opts.password, opts.url, 
sslverify=False)
 products = get_products(testopia, opts, logger, config, **kwargs)
 
-- 
2.11.0

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

[yocto] QtWebEngine cannot show google sites due to certificate errors

2017-05-16 Thread Andrea Picaro 
Hello, i compiled Yocto Morty for an mx6 machine.
QtWebEngine works fine for all sites (included https by ignoring
certificate errors) apart
from google sites.
I've found other info about this issue googling around but it seemed
to be solved in latest chromium builds and none of the solutions tested
gave results.
All google sites gives ERR_INSECURE_RESPONSE and i see this error in
console:
ERROR:cert_verify_proc_openssl.cc(238)] X509 Verification error certificate
has expired : 10 : 3 : 2

Any hint would much appreciated
Thanks

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

[yocto] Add 'mongodb' package in Yocto (Jethro branch)

2017-05-16 Thread Jaymin D 
Hi Team,

I want to add 'mongodb' package into my current Yocto (Jethro branch) build.

I have tried to add in - CORE_IMAGE_EXTRA_INSTALL += " mongodb", also tried
to add " boost" package too. But, it couldn't compile.

The error was:

*ERROR: Required build target 'core-image-base' has no buildable providers.*
*Missing or unbuildable dependency chain was: ['core-image-base', 'mongo']*

I have also tried this - "
http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/mongodb/mongodb_git.bb?h=master
"

But, bitbake was failed.

What would be the possible reason of failing the bitbake?
In which file I have to make changes for adding the 'mongodb' package?

All suggestions are welcomed.

Thank You,
Jaymin
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Add 'mongodb' package in Yocto (Jethro branch)

2017-05-16 Thread Khem Raj 
On Thu, May 11, 2017 at 5:55 AM, Jaymin D  wrote:
> Hi Team,
>
> I want to add 'mongodb' package into my current Yocto (Jethro branch) build.
>
> I have tried to add in - CORE_IMAGE_EXTRA_INSTALL += " mongodb", also tried
> to add " boost" package too. But, it couldn't compile.
>
> The error was:
>
> ERROR: Required build target 'core-image-base' has no buildable providers.
> Missing or unbuildable dependency chain was: ['core-image-base', 'mongo']
>
> I have also tried this -
> "http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/mongodb/mongodb_git.bb?h=master";
>
> But, bitbake was failed.
>
> What would be the possible reason of failing the bitbake?
> In which file I have to make changes for adding the 'mongodb' package?
>
> All suggestions are welcomed.

in jethro mongodb recipe seems to be blacklisted. So you have to ensure
that the reason for blacklisting it is addressed before you can use it

>
> Thank You,
> Jaymin
>
> --
> ___
> 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] [meta-selinux][PATCH] systemd: no need to inherit enable-selinux

2017-05-16 Thread Huang, Jie (Jackie) 


> -Original Message-
> From: Joe MacDonald [mailto:joe_macdon...@mentor.com]
> Sent: Tuesday, May 16, 2017 19:55
> To: Huang, Jie (Jackie)
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] [meta-selinux][PATCH] systemd: no need to inherit enable-
> selinux
> 
> [RE: [yocto] [meta-selinux][PATCH] systemd: no need to inherit enable-selinux]
> On 17.05.08 (Mon 01:40) Huang, Jie (Jackie) wrote:
> 
> >
> >
> > > -Original Message-
> > > From: Joe MacDonald [mailto:joe_macdon...@mentor.com]
> > > Sent: Tuesday, May 02, 2017 21:14
> > > To: Huang, Jie (Jackie)
> > > Cc: yocto@yoctoproject.org
> > > Subject: Re: [yocto] [meta-selinux][PATCH] systemd: no need to inherit
> enable-
> > > selinux
> > >
> > > [[yocto] [meta-selinux][PATCH] systemd: no need to inherit enable-selinux]
> On
> > > 17.02.22 (Wed 14:44) jackie.hu...@windriver.com wrote:
> > >
> > > > From: Jackie Huang 
> > > >
> > > > The selinux PACKAGECONFIG is properly handled in
> > > > the recipe in oe-core, no need to inherit the
> > > > enable-selinux bbclass.
> > >
> > > That might be true, but other than belt-and-suspenders, what's the
> > > harm in this being in the recipe?  I don't necessarily think it's an
> > > invalid change but my quick count shows ~44 instances of 'inherit
> > > enable-selinux' and 'inherit with-selinux' in meta-selinux, why's this
> > > one significant?
> >
> > That's because I have a patch to change the PACKAGECONFIG for selinux
> > in oe-core to fix a dependency issue:
> >
> > -PACKAGECONFIG[selinux] = "--enable-selinux,--disable-selinux,libselinux"
> > +PACKAGECONFIG[selinux] = "--enable-selinux,--disable-
> selinux,libselinux,initscripts-sushell"
> >
> > But it would be overrode by the one in enable-selinux.bbclass:
> > $ grep PACKAGECONFIG enable-selinux.bbclass
> > PACKAGECONFIG_append = " ${@target_selinux(d)}"
> > PACKAGECONFIG[selinux] = "--enable-selinux,--disable-selinux,libselinux,"
> >
> > So I need to remove the inherit here in meta-selinux.
> 
> Sorry, this fell between the cracks.
> 
> So, let me make sure I understand what you're saying.  This oe-core
> commit:
> 
> commit 1881c5e0c426a193630e5eed5b629b69ff3741d5
> Author: Kai Kang 
> Date:   Wed Jul 8 14:26:01 2015 +0800
> 
> systemd: add PACKAGECONFIG selinux
> 
> Add PACKAGECONFIG 'selinux' for systemd. debug-shell.service starts
> different shell according whether selinux is enabled.
> 
> (From OE-Core rev: 3d1aa27191fe4c21428eaf4ae036acb1496b7df7)
> 
> Signed-off-by: Kai Kang 
> Signed-off-by: Richard Purdie 
> 
> conflicts with the --enable/--disable settings in meta-selinux and  you
> want to remove the setting in meta-selinux?  Again, I don't specifically
> object to this, but I'd like to understand the why of it.  Is there a
> valid scenario to include meta-selinux in your project but have selinux
> disabled?  If so, I would think the settings in meta-selinux should

The conflicts is not the --enable/--disable settings, it's the dependency:

oe-core: PACKAGECONFIG[selinux] = 
"--enable-selinux,--disable-selinux,libselinux,initscripts-sushell"
meta-selinux: PACKAGECONFIG[selinux] = 
"--enable-selinux,--disable-selinux,libselinux,"

There is an extra runtime dependency on initscripts-sushell (which is reauired 
by debug-shell.service),
so if inheriting the enable-selinux in meta-selinux, the selinux will still be 
enabled, but the dependency
on initscripts-sushell will be lost.

> still take precedence.  Otherwise, I'm confused why the other 40-ish

Others don't have the extra dependency, the setting in oe-core and
meta-selinux are the same(at least for now), so others aren't covered.

Thanks,
Jackie

> cases aren't also covered.  I haven't investigated, but are all the
> others in non-oe-core layers, maybe?
> 
> Thanks,
> -J.
> 
> >
> > Thanks,
> > Jackie
> >
> > >
> > > -J.
> > >
> > > >
> > > > Signed-off-by: Jackie Huang 
> > > > ---
> > > >  recipes-core/systemd/systemd_%.bbappend | 1 -
> > > >  1 file changed, 1 deletion(-)
> > > >
> > > > diff --git a/recipes-core/systemd/systemd_%.bbappend b/recipes-
> > > core/systemd/systemd_%.bbappend
> > > > index 8d9029b..f1bdaf8 100644
> > > > --- a/recipes-core/systemd/systemd_%.bbappend
> > > > +++ b/recipes-core/systemd/systemd_%.bbappend
> > > > @@ -1,2 +1 @@
> > > >  inherit enable-audit
> > > > -inherit enable-selinux
> > > > --
> > > > 2.8.3
> > > >
> > > --
> > > -Joe MacDonald.
> > > :wq
> 
> --
> -Joe MacDonald.
> :wq
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH v3 1/3] recipes-multimedia: add Rockchip MPP library

2017-05-16 Thread Romain Perier 
Hello,


Le 16/05/2017 à 20:44, Trevor Woerner a écrit :
> Randy,
>
> Neither of the issues that were identified in your v2 of this patch were
> addressed in this v3. Namely:
>
> 1) please use your real name (first, last) in your signed-off-by line
> 2) please don't create a package from this recipe whose name doesn't include
>the recipe name (i.e. please don't create "rockchip-vpu" from a recipe
>"rockchip-mpp"), suggestions were provided
>
> Aside from the email headers and the version of git used, this patch is
> identical to the v2 you submitted.
>
> Best regards,
>   Trevor
+1

And please, include a changelog in your new version, at least in the
cover letter, something like:

Changes in v3:
- Item1 fixed
- Item2 fixed

Changes in v2:
- Item1 fixed
- Item2 fixed


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