Re: [yocto] [meta-oic][PATCH] Update for IoTivity 1.1.1
On 3 August 2016 at 22:09, Philippe Coval
wrote:
> +INSANE_SKIP_${PN}-dev = "ldflags"
> +INSANE_SKIP_${PN}-plugins-samples = "ldflags"
> +INSANE_SKIP_${PN}-resource = "ldflags"
> +INSANE_SKIP_${PN}-resource-samples = "ldflags"
> +INSANE_SKIP_${PN}-service = "ldflags"
> +INSANE_SKIP_${PN}-service-samples = "ldflags"
> +INSANE_SKIP_${PN}-tests = "ldflags"
>
This happens because the recipe isn't respecting LDFLAGS. You really
should be ensuring LDFLAGS is used by the build instead of skipping the
warning.
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Install multi files in shared area Error
Hi all ERROR: The recipe libnetconf is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /mnt/c1/git/poky/build-toaster-5/tmp/sysroots/qemux86/pkgdata/runtime/libxml2 Matched in manifest-qemux86-libxml2.packagedata /mnt/c1/git/poky/build-toaster-5/tmp/sysroots/qemux86/pkgdata/runtime/libxslt Matched in manifest-qemux86-libxslt.packagedata /mnt/c1/git/poky/build-toaster-5/tmp/sysroots/qemux86/pkgdata/runtime/openssl Matched in manifest-qemux86-openssl.packagedata .. ERROR: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. DEBUG: Python function sstate_task_postfunc finished ERROR: Function failed: sstate_task_postfunc Which tmp dir should I wipe out?Thanks Richard Zhang -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Install multi files in shared area Error
On 4 August 2016 at 09:46, Richard Zhang wrote: > Which tmp dir should I wipe out?Thanks > > The tmp/ inside your build directory. If it happens again, then libnetconf is doing something very wrong. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-virtualization][PATCH] Upgrade libvirt to 1.3.5
From: Kai Kang
* The ptest still have 8 failed items in 124 cases.
Kai Kang (1):
libvirt: upgrade 1.3.2 -> 1.3.5
.../0001-to-fix-build-error.patch | 0
recipes-extended/libvirt/libvirt-python.inc| 5 +-
.../0001-fix-crash-in-getAllDomainStats.patch | 57 --
...vert-build-add-prefix-to-SYSTEMD_UNIT_DIR.patch | 16 --
.../libvirt/libvirt/install-missing-file.patch | 12 -
recipes-extended/libvirt/libvirt/runptest.patch| 34 +++--
.../libvirt/{libvirt_1.3.2.bb => libvirt_1.3.5.bb} | 10 ++--
7 files changed, 47 insertions(+), 87 deletions(-)
rename recipes-extended/libvirt/{libvirt-1.3.2 =>
libvirt-1.3.5}/0001-to-fix-build-error.patch (100%)
delete mode 100644
recipes-extended/libvirt/libvirt/0001-fix-crash-in-getAllDomainStats.patch
rename recipes-extended/libvirt/{libvirt_1.3.2.bb => libvirt_1.3.5.bb} (97%)
--
2.9.2.368.g08bb350
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] libvirt: upgrade 1.3.2 -> 1.3.5
From: Kai Kang
Upgrade libvirt from 1.3.2 to 1.3.5.
* update checksums and remove PR
* remove trailing whitespace
* remove backport patch 0001-fix-crash-in-getAllDomainStats.patch
* update context of patches
* remove libvirtd.socket from SYSTEMD_SERVICE which doesn't exist anymore
* install test data which ptest requires
Signed-off-by: Kai Kang
---
.../0001-to-fix-build-error.patch | 0
recipes-extended/libvirt/libvirt-python.inc| 5 +-
.../0001-fix-crash-in-getAllDomainStats.patch | 57 --
...vert-build-add-prefix-to-SYSTEMD_UNIT_DIR.patch | 16 --
.../libvirt/libvirt/install-missing-file.patch | 12 -
recipes-extended/libvirt/libvirt/runptest.patch| 34 +++--
.../libvirt/{libvirt_1.3.2.bb => libvirt_1.3.5.bb} | 10 ++--
7 files changed, 47 insertions(+), 87 deletions(-)
rename recipes-extended/libvirt/{libvirt-1.3.2 =>
libvirt-1.3.5}/0001-to-fix-build-error.patch (100%)
delete mode 100644
recipes-extended/libvirt/libvirt/0001-fix-crash-in-getAllDomainStats.patch
rename recipes-extended/libvirt/{libvirt_1.3.2.bb => libvirt_1.3.5.bb} (97%)
diff --git
a/recipes-extended/libvirt/libvirt-1.3.2/0001-to-fix-build-error.patch
b/recipes-extended/libvirt/libvirt-1.3.5/0001-to-fix-build-error.patch
similarity index 100%
rename from recipes-extended/libvirt/libvirt-1.3.2/0001-to-fix-build-error.patch
rename to recipes-extended/libvirt/libvirt-1.3.5/0001-to-fix-build-error.patch
diff --git a/recipes-extended/libvirt/libvirt-python.inc
b/recipes-extended/libvirt/libvirt-python.inc
index 405d5f7..7fcce43 100644
--- a/recipes-extended/libvirt/libvirt-python.inc
+++ b/recipes-extended/libvirt/libvirt-python.inc
@@ -17,10 +17,9 @@ FILES_${PN}-python = "${bindir}/* ${libdir}/*
${libdir}/${PYTHON_DIR}/*"
SRC_URI +=
"http://libvirt.org/sources/python/libvirt-python-${PV}.tar.gz;name=libvirt_python";
SRC_URI += "file://libvirt_api_xml_path.patch;patchdir=../libvirt-python-${PV}"
-SRC_URI +=
"file://0001-fix-crash-in-getAllDomainStats.patch;patchdir=../libvirt-python-${PV}"
-SRC_URI[libvirt_python.md5sum] = "ed018c714d7ddbe93221c796dff283ed"
-SRC_URI[libvirt_python.sha256sum] =
"6d35ae9e7801573393b9c92471f39e6700d479f10b641df81d041b469f160bf8"
+SRC_URI[libvirt_python.md5sum] = "4dbd7ef9ee9c4dea5887b5b31eb04529"
+SRC_URI[libvirt_python.sha256sum] =
"a0508a57637fd18a3584fb9d2322fb172f65708c9db16e0438a70eb0f36fa5c2"
export LIBVIRT_API_PATH = "${S}/docs/libvirt-api.xml"
export LIBVIRT_CFLAGS = "-I${S}/include"
diff --git
a/recipes-extended/libvirt/libvirt/0001-fix-crash-in-getAllDomainStats.patch
b/recipes-extended/libvirt/libvirt/0001-fix-crash-in-getAllDomainStats.patch
deleted file mode 100644
index 0583a94..000
--- a/recipes-extended/libvirt/libvirt/0001-fix-crash-in-getAllDomainStats.patch
+++ /dev/null
@@ -1,57 +0,0 @@
-From e9c4e2abffef007a28112ebb40a9586b0128f10b Mon Sep 17 00:00:00 2001
-From: Pavel Hrdina
-Date: Mon, 18 Apr 2016 16:53:50 +0200
-Subject: [PATCH] fix crash in getAllDomainStats
-
-Upstream-Status: Backport
-
-Commits 1d39dbaf and 827ed9b4 broke the libvirt-python API by removing
-virDomainRef() and virDomainFree(). virDomainStatsRecordListFree() will
-free that domain pointer and later when virDomain (python object) call
-its destructor and tries to free that same pointer again.
-
-Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1326839
-
-Signed-off-by: Pavel Hrdina
- libvirt-override.c | 8 +++-
- 1 file changed, 7 insertions(+), 1 deletion(-)
-
-diff --git a/libvirt-override.c b/libvirt-override.c
-index 4640ed5..2de95ce 100644
a/libvirt-override.c
-+++ b/libvirt-override.c
-@@ -8381,6 +8381,7 @@ convertDomainStatsRecord(virDomainStatsRecordPtr
*records,
- PyObject *py_retval;
- PyObject *py_record;
- PyObject *py_record_stats = NULL;
-+virDomainPtr dom = NULL;
- size_t i;
-
- if (!(py_retval = PyList_New(nrecords)))
-@@ -8392,9 +8393,12 @@ convertDomainStatsRecord(virDomainStatsRecordPtr
*records,
-
- VIR_PY_LIST_SET_GOTO(py_retval, i, py_record, error);
-
-+dom = records[i]->dom;
-+virDomainRef(dom);
- VIR_PY_TUPLE_SET_GOTO(py_record, 0,
-- libvirt_virDomainPtrWrap(records[i]->dom),
-+ libvirt_virDomainPtrWrap(dom),
- error);
-+dom = NULL;
-
- if (!(py_record_stats = getPyVirTypedParameter(records[i]->params,
-records[i]->nparams)))
-@@ -8406,6 +8410,8 @@ convertDomainStatsRecord(virDomainStatsRecordPtr
*records,
- return py_retval;
-
- error:
-+if (dom)
-+virDomainFree(dom);
- Py_XDECREF(py_retval);
- return NULL;
- }
---
-2.8.1
-
diff --git
a/recipes-extended/libvirt/libvirt/Revert-build-add-prefix-to-SYSTEMD_UNIT_DIR.patch
b/recipes-extended/libvirt/libvirt/Revert-build-add-prefix-to-SYSTEMD_UNIT_DIR.patch
index 16c3a1
[yocto] Layer priorities & package selection
Hello all, We are having two yocto layers in our project. One is SoC specific layer and the other is the meta-ivi. Now we have two packages provided by both these layers. wayland_1.9.0 & weston_1.9.0. We want both these packages from the SoC specific layer and not the ones that are coming from meta-ivi. The reason being that the SoC vendor has done some modifications for hw acceleration and stuff like that. Since meta-ivi is having higher priority( Priority: 7) than the SoC specific layer(Priority : 6) , naturally these packages are provided by meta-ivi and not the Soc layer which we actually want. How to modify the layer priority without touching the layer specific conf file ? Can we have a append to the layer conf file ? meta-ivi: [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$ find . -name "wayland*" ./meta-ivi/recipes-graphics/wayland ./meta-ivi/recipes-graphics/wayland/wayland_1.9.0.bb [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$ find . -name "weston*" ./meta-ivi/recipes-graphics/wayland/weston ./meta-ivi/recipes-graphics/wayland/weston/weston.png ./meta-ivi/recipes-graphics/wayland/weston/weston.desktop ./meta-ivi/recipes-graphics/wayland/weston_1.9.0.bb ./meta-ivi/recipes-graphics/wayland/weston_1.9.0.bbappend ./meta-ivi-bsp/recipes-graphics/weston meta-renesas: [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$ find . -name "wayland*" ./meta-rcar-gen3/recipes-graphics/wayland ./meta-rcar-gen3/recipes-graphics/wayland/wayland_1.9.0.bb [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$ find . -name "weston*" ./meta-rcar-gen3/recipes-graphics/wayland/weston.inc ./meta-rcar-gen3/recipes-graphics/wayland/weston-init.bbappend ./meta-rcar-gen3/recipes-graphics/wayland/weston ./meta-rcar-gen3/recipes-graphics/wayland/weston/weston.png ./meta-rcar-gen3/recipes-graphics/wayland/weston/weston.desktop ./meta-rcar-gen3/recipes-graphics/wayland/weston_%.bbappend ./meta-rcar-gen3/recipes-graphics/wayland/weston-init ./meta-rcar-gen3/recipes-graphics/wayland/weston-init/weston.service ./meta-rcar-gen3/recipes-graphics/wayland/weston_1.9.0.bb ./meta-rcar-gen3/recipes-graphics/wayland/weston_1.9.0.bbappend Thanks & Regards, Hari Prasath -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Layer priorities & package selection
On Thu, Aug 4, 2016 at 9:28 AM, Gujulan Elango, Hari Prasath (H.) wrote: > > Hello all, > > > We are having two yocto layers in our project. One is SoC specific layer and > the other is the meta-ivi. Now we have two packages provided by both these > layers. wayland_1.9.0 & weston_1.9.0. We want both these packages from the > SoC specific layer and not the ones that are coming from meta-ivi. The reason > being that the SoC vendor has done some modifications for hw acceleration and > stuff like that. Since meta-ivi is having higher priority( Priority: 7) than > the SoC specific layer(Priority : 6) , naturally these packages are provided > by meta-ivi and not the Soc layer which we actually want. > > > How to modify the layer priority without touching the layer specific conf > file ? Can we have a append to the layer conf file ? Try moving the recipe to your layer (provided yours is of higher priority). I often go with per project BSP layers that adjust the low level pieces of the target, such as kernel configs etc., while applications stay in application-only layer. Another option that I see is to set BBMASK = "meta-ivi/recipes-graphics/wayland/" in local.conf, but that's a bit ugly, hence I'd say it's a temporary solution only. > > > > meta-ivi: > > [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$ > find . -name "wayland*" > ./meta-ivi/recipes-graphics/wayland > ./meta-ivi/recipes-graphics/wayland/wayland_1.9.0.bb > > > [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$ > find . -name "weston*" > ./meta-ivi/recipes-graphics/wayland/weston > ./meta-ivi/recipes-graphics/wayland/weston/weston.png > ./meta-ivi/recipes-graphics/wayland/weston/weston.desktop > ./meta-ivi/recipes-graphics/wayland/weston_1.9.0.bb > ./meta-ivi/recipes-graphics/wayland/weston_1.9.0.bbappend > ./meta-ivi-bsp/recipes-graphics/weston > > > > meta-renesas: > > > > [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$ > find . -name "wayland*" > ./meta-rcar-gen3/recipes-graphics/wayland > ./meta-rcar-gen3/recipes-graphics/wayland/wayland_1.9.0.bb > > > > [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$ > find . -name "weston*" > ./meta-rcar-gen3/recipes-graphics/wayland/weston.inc > ./meta-rcar-gen3/recipes-graphics/wayland/weston-init.bbappend > ./meta-rcar-gen3/recipes-graphics/wayland/weston > ./meta-rcar-gen3/recipes-graphics/wayland/weston/weston.png > ./meta-rcar-gen3/recipes-graphics/wayland/weston/weston.desktop > ./meta-rcar-gen3/recipes-graphics/wayland/weston_%.bbappend > ./meta-rcar-gen3/recipes-graphics/wayland/weston-init > ./meta-rcar-gen3/recipes-graphics/wayland/weston-init/weston.service > ./meta-rcar-gen3/recipes-graphics/wayland/weston_1.9.0.bb > ./meta-rcar-gen3/recipes-graphics/wayland/weston_1.9.0.bbappend > > > > Thanks & Regards, > > Hari Prasath > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- Maciej Borzecki RnDity -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [GIT PULL | BXT-REBASE] USB Perihperal RTPM fixes
These requests need to go to the linux-yo...@yoctoproject.org list. This is part of the open source process and needs to be followed for transparency. Sending it to me or directly to Bruce will not work. Also, please understand that Bruce is on vacation this week, he will merge things time permitting, but his gmail email must also be CC'ed otherwise he may not see it. (bruce.ashfi...@gmail.com). Sau! On Thu, 2016-08-04 at 07:37 -0700, Kumar, Anil K wrote: > + Saul > > Anil K Kumar, PhD > Principal Engineer > Lead System Architect > Makers & Innovators Group (MIG) / New Technology Group (NTG) > > > -Original Message- > From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com] > Sent: Thursday, August 4, 2016 4:34 AM > To: Ashfield, Bruce (Wind River) > Cc: Kumar, Anil K ; Renganathan, Prabu .renganat...@intel.com>; Svahn, Kai ; Ponnusamy, > Siva Prasath ; Hart, Patrick J rick.j.h...@intel.com>; Leblanc, Darrell ; > yocto@yoctoproject.org > Subject: [GIT PULL | BXT-REBASE] USB Perihperal RTPM fixes > > > Hi Bruce, > > please pull following branch and apply on top of bxt-rebase. It fixes > a few issues with runtime PM with drivers/usb/dwc3/ > > Best > > The following changes since commit > 17a1643e70318316c4cd275d1c1f252d0a97f46f: > > Merge branch 'standard/intel/base' into standard/intel/bxt-rebase > (2016-07-25 23:56:53 -0400) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git bxt- > testing-pm > > for you to fetch changes up to > fea0e55419272d6185c1d19a1a5b89e0545cbc39: > > usb: dwc3: pci: call _DSM for suspend/resume (2016-08-04 09:35:44 > +0300) > > > Felipe Balbi (5): > usb: dwc3: pci: runtime_resume child device > usb: dwc3: core: allow device to runtime_suspend several times > usb: dwc3: gadget: increment request->actual once > usb: dwc3: make sure UX_EXIT_PX is cleared > usb: dwc3: pci: call _DSM for suspend/resume > > drivers/usb/dwc3/core.c | 7 +++ > drivers/usb/dwc3/core.h | 1 + > drivers/usb/dwc3/dwc3-pci.c | 105 > +--- > drivers/usb/dwc3/gadget.c | 19 > 4 files changed, 107 insertions(+), 25 deletions(-) > > > -- > balbi -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] Update for IoTivity 1.1.1
* Inspired from iotivity_1.1.0.bb.
* Tinycobor is updated to v0.2.1.
* Unused libs are dropped.
* QA checks are disabled
to support Yocto jethro base and later,
without it packaging task will fail and report this message :
ERROR: QA Issue: No GNU_HASH in the elf binary
* Security is still not emabled.
* Note this version of recipe is using upstream's git repo as source
as it's smarter for upstream/downstream cooperation
More at: https://wiki.iotivity.org/yocto .
Change-Id: Ib6f69c24434615d178ccef15cad96142e2b837aa
Cc: iotivity-...@lists.iotivity.org
Cc: yocto@yoctoproject.org
Credit-to: Kishen Maloor
Origin: https://github.com/tizenteam/meta-oic
Signed-off-by: Philippe Coval
---
recipes-core/iotivity/iotivity_1.1.1.bb | 503
1 file changed, 503 insertions(+)
create mode 100644 recipes-core/iotivity/iotivity_1.1.1.bb
diff --git a/recipes-core/iotivity/iotivity_1.1.1.bb
b/recipes-core/iotivity/iotivity_1.1.1.bb
new file mode 100644
index 000..d47046f
--- /dev/null
+++ b/recipes-core/iotivity/iotivity_1.1.1.bb
@@ -0,0 +1,503 @@
+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"
+EXTRANATIVEPATH += "chrpath-native"
+SECTION = "libs"
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = "file://LICENSE.md;md5=22bf216f3077c279aed7b36b1fa9e6d1"
+
+SRCREV = "83801cb90a9b96fef2726de72f48deb7180afef6"
+TINYCBOR_SRCREV = "358a7e42ab1ed421a68e699d8d8359340bcfacbd"
+
+SRC_URI =
"git://github.com/iotivity/iotivity.git;protocol=http;nobranch=1;destsuffix=${S}
\
+
https://github.com/01org/tinycbor/archive/${TINYCBOR_SRCREV}.zip;name=tinycbor;destsuffix=${S}
\
+ https://googletest.googlecode.com/files/gtest-1.7.0.zip;name=gtest \
+
http://www.sqlite.org/2015/sqlite-amalgamation-3081101.zip;name=sqlite3 \
+ "
+SRC_URI[gtest.md5sum] = "2d6ec8ccdf5c46b05ba54a9fd1d130d7"
+SRC_URI[gtest.sha256sum] =
"247ca18dd83f53deb1328be17e4b1be31514cedfc1e3424f672bf11fd7e0d60d"
+
+SRC_URI[tinycbor.md5sum] = "906cd113e90515240d62bd185c714cc6"
+SRC_URI[tinycbor.sha256sum] =
"b5b002f5540e44c995ee57c62604e85c32525b79fb720dceb422265e80aa9cba"
+
+SRC_URI[sqlite3.md5sum] = "94907e831502e2080b76e281cfa24dde"
+SRC_URI[sqlite3.sha256sum] =
"a3b0c07d1398d60ae9d21c2cc7f9be6b1bc5b0168cd94c321ede9a0fce2b3cd7"
+
+inherit scons
+
+python () {
+IOTIVITY_TARGET_ARCH = d.getVar("TARGET_ARCH", True)
+EXTRA_OESCONS = "TARGET_OS=yocto TARGET_ARCH=" + IOTIVITY_TARGET_ARCH + "
RELEASE=1 WITH_RD=1 ROUTING=GW"
+d.setVar("EXTRA_OESCONS", EXTRA_OESCONS)
+d.setVar("IOTIVITY_TARGET_ARCH", IOTIVITY_TARGET_ARCH)
+}
+
+IOTIVITY_BIN_DIR = "/opt/iotivity"
+IOTIVITY_BIN_DIR_D = "${D}${IOTIVITY_BIN_DIR}"
+
+do_compile_prepend() {
+if [ ! -f "${S}/extlibs/sqlite3/sqlite3.c" ]; then
+cp ${WORKDIR}/sqlite-amalgamation-3081101/sqlite3.c
${S}/extlibs/sqlite3
+cp ${WORKDIR}/sqlite-amalgamation-3081101/sqlite3.h
${S}/extlibs/sqlite3
+fi
+if [ ! -d "${S}/extlibs/gtest/gtest-1.7.0/" ]; then
+cp -rf ${WORKDIR}/gtest-1.7.0 ${S}/extlibs/gtest/
+fi
+
+if [ ! -d "${S}/extlibs/tinycbor/tinycbor" ] ; then
+cp -rf ${WORKDIR}/tinycbor-* ${S}/extlibs/tinycbor/tinycbor
+fi
+
+
+export PKG_CONFIG_PATH="${PKG_CONFIG_PATH}"
+export PKG_CONFIG="PKG_CONFIG_SYSROOT_DIR=\"${PKG_CONFIG_SYSROOT_DIR}\"
pkg-config"
+}
+
+make_dir() {
+install -d $1
+}
+
+copy_file() {
+install -c -m 444 $1 $2
+}
+
+copy_exec() {
+install -c -m 555 $1 $2
+}
+
+copy_file_recursive() {
+cd $1 && find . -type d -exec install -d $2/"{}" \;
+cd $1 && find . -type f -exec install -c -m 444 "{}" $2/"{}" \;
+}
+
+copy_exec_recursive() {
+cd $1 && find . -executable -exec install -c -m 555 "{}" $2/"{}" \;
+}
+
+do_install() {
+make_dir ${D}${libdir}
+#Resource
+#C++ APIs
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/liboc.so
${D}${libdir}
+
+#Logger
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/liboc_logger.so
${D}${libdir}
+copy_file
${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/liboc_logger_core.so
${D}${libdir}
+
+#CSDK Shared
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/liboctbstack.so
${D}${libdir}
+
+#CSDK Static
+copy_file
${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/libconnectivity_abstraction.a
${D}${libdir}
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/libcoap.a
${D}${libdir}
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/liboctbstack.a
${D}${libdir}
+copy_file ${S}/out/yocto/${IOTIVITY_TARGET_ARCH}/release/libc_common.a
${D}${libdir}
+copy_file ${S}/out
[yocto] [GIT PULL | BXT-REBASE] USB Perihperal RTPM fixes
Hi Bruce, please pull following branch and apply on top of bxt-rebase. It fixes a few issues with runtime PM with drivers/usb/dwc3/ Best The following changes since commit 17a1643e70318316c4cd275d1c1f252d0a97f46f: Merge branch 'standard/intel/base' into standard/intel/bxt-rebase (2016-07-25 23:56:53 -0400) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git bxt-testing-pm for you to fetch changes up to fea0e55419272d6185c1d19a1a5b89e0545cbc39: usb: dwc3: pci: call _DSM for suspend/resume (2016-08-04 09:35:44 +0300) Felipe Balbi (5): usb: dwc3: pci: runtime_resume child device usb: dwc3: core: allow device to runtime_suspend several times usb: dwc3: gadget: increment request->actual once usb: dwc3: make sure UX_EXIT_PX is cleared usb: dwc3: pci: call _DSM for suspend/resume drivers/usb/dwc3/core.c | 7 +++ drivers/usb/dwc3/core.h | 1 + drivers/usb/dwc3/dwc3-pci.c | 105 +--- drivers/usb/dwc3/gadget.c | 19 4 files changed, 107 insertions(+), 25 deletions(-) -- balbi signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [GIT PULL | BXT-REBASE] USB Perihperal RTPM fixes
+ Saul Anil K Kumar, PhD Principal Engineer Lead System Architect Makers & Innovators Group (MIG) / New Technology Group (NTG) -Original Message- From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com] Sent: Thursday, August 4, 2016 4:34 AM To: Ashfield, Bruce (Wind River) Cc: Kumar, Anil K ; Renganathan, Prabu ; Svahn, Kai ; Ponnusamy, Siva Prasath ; Hart, Patrick J ; Leblanc, Darrell ; yocto@yoctoproject.org Subject: [GIT PULL | BXT-REBASE] USB Perihperal RTPM fixes Hi Bruce, please pull following branch and apply on top of bxt-rebase. It fixes a few issues with runtime PM with drivers/usb/dwc3/ Best The following changes since commit 17a1643e70318316c4cd275d1c1f252d0a97f46f: Merge branch 'standard/intel/base' into standard/intel/bxt-rebase (2016-07-25 23:56:53 -0400) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git bxt-testing-pm for you to fetch changes up to fea0e55419272d6185c1d19a1a5b89e0545cbc39: usb: dwc3: pci: call _DSM for suspend/resume (2016-08-04 09:35:44 +0300) Felipe Balbi (5): usb: dwc3: pci: runtime_resume child device usb: dwc3: core: allow device to runtime_suspend several times usb: dwc3: gadget: increment request->actual once usb: dwc3: make sure UX_EXIT_PX is cleared usb: dwc3: pci: call _DSM for suspend/resume drivers/usb/dwc3/core.c | 7 +++ drivers/usb/dwc3/core.h | 1 + drivers/usb/dwc3/dwc3-pci.c | 105 +--- drivers/usb/dwc3/gadget.c | 19 4 files changed, 107 insertions(+), 25 deletions(-) -- balbi -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [GIT PULL | BXT-REBASE] USB Perihperal RTPM fixes
Anil K Kumar, PhD Principal Engineer Lead System Architect Makers & Innovators Group (MIG) / New Technology Group (NTG) -Original Message- From: Wold, Saul Sent: Thursday, August 4, 2016 8:41 AM To: Kumar, Anil K ; Felipe Balbi ; Ashfield, Bruce (Wind River) Cc: Renganathan, Prabu ; Svahn, Kai ; Ponnusamy, Siva Prasath ; Hart, Patrick J ; Leblanc, Darrell ; yocto@yoctoproject.org Subject: Re: [GIT PULL | BXT-REBASE] USB Perihperal RTPM fixes These requests need to go to the linux-yo...@yoctoproject.org list. This is part of the open source process and needs to be followed for transparency. Sending it to me or directly to Bruce will not work. Also, please understand that Bruce is on vacation this week, he will merge things time permitting, but his gmail email must also be CC'ed otherwise he may not see it. (bruce.ashfi...@gmail.com). Sau! On Thu, 2016-08-04 at 07:37 -0700, Kumar, Anil K wrote: > + Saul > > Anil K Kumar, PhD > Principal Engineer > Lead System Architect > Makers & Innovators Group (MIG) / New Technology Group (NTG) > > > -Original Message- > From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com] > Sent: Thursday, August 4, 2016 4:34 AM > To: Ashfield, Bruce (Wind River) > Cc: Kumar, Anil K ; Renganathan, Prabu .renganat...@intel.com>; Svahn, Kai ; Ponnusamy, > Siva Prasath ; Hart, Patrick J rick.j.h...@intel.com>; Leblanc, Darrell ; > yocto@yoctoproject.org > Subject: [GIT PULL | BXT-REBASE] USB Perihperal RTPM fixes > > > Hi Bruce, > > please pull following branch and apply on top of bxt-rebase. It fixes > a few issues with runtime PM with drivers/usb/dwc3/ > > Best > > The following changes since commit > 17a1643e70318316c4cd275d1c1f252d0a97f46f: > > Merge branch 'standard/intel/base' into standard/intel/bxt-rebase > (2016-07-25 23:56:53 -0400) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git bxt- > testing-pm > > for you to fetch changes up to > fea0e55419272d6185c1d19a1a5b89e0545cbc39: > > usb: dwc3: pci: call _DSM for suspend/resume (2016-08-04 09:35:44 > +0300) > > > Felipe Balbi (5): > usb: dwc3: pci: runtime_resume child device > usb: dwc3: core: allow device to runtime_suspend several times > usb: dwc3: gadget: increment request->actual once > usb: dwc3: make sure UX_EXIT_PX is cleared > usb: dwc3: pci: call _DSM for suspend/resume > > drivers/usb/dwc3/core.c | 7 +++ > drivers/usb/dwc3/core.h | 1 + > drivers/usb/dwc3/dwc3-pci.c | 105 > +--- > drivers/usb/dwc3/gadget.c | 19 > 4 files changed, 107 insertions(+), 25 deletions(-) > > > -- > balbi -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] where to find license files?
I'm working on getting a list of license files and I don't know where to get the exact text of each license. Is there a place where this is provided by yocto? For example, is there some directory which has all the license files? I see there's an md5sum for each file so I assume this is the case. Thanks in advance. Frederick Ollinger -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] where to find license files?
On 2016-08-04 18:47, Fred Ollinger wrote: I'm working on getting a list of license files and I don't know where to get the exact text of each license. Is there a place where this is provided by yocto? For example, is there some directory which has all the license files? I see there's an md5sum for each file so I assume this is the case. After you build an image, look in /tmp/deploy/licenses/* These are the exact licenses used by your image -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Layer priorities & package selection
Hi, On 2016-08-04 16:21, Maciej Borzęcki wrote: Another option that I see is to set BBMASK = "meta-ivi/recipes-graphics/wayland/" in local.conf, but that's a bit ugly, hence I'd say it's a temporary solution only. BBMASK does not seem to apply only to local.conf anymore[1], so this might not just be a temporary solution. [1] https://lists.yoctoproject.org/pipermail/poky/2016-January/010358.html Regards, Robert -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] libvirt: upgrade 1.3.2 -> 1.3.5
Wrong mailing list (it should be meta-virtualizat...@yoctoproject.org), but
I can
pick up this change from here
No need to resend.
Bruce
On Thu, Aug 4, 2016 at 5:38 AM, wrote:
> From: Kai Kang
>
> Upgrade libvirt from 1.3.2 to 1.3.5.
>
> * update checksums and remove PR
> * remove trailing whitespace
> * remove backport patch 0001-fix-crash-in-getAllDomainStats.patch
> * update context of patches
> * remove libvirtd.socket from SYSTEMD_SERVICE which doesn't exist anymore
> * install test data which ptest requires
>
> Signed-off-by: Kai Kang
> ---
> .../0001-to-fix-build-error.patch | 0
> recipes-extended/libvirt/libvirt-python.inc| 5 +-
> .../0001-fix-crash-in-getAllDomainStats.patch | 57
> --
> ...vert-build-add-prefix-to-SYSTEMD_UNIT_DIR.patch | 16 --
> .../libvirt/libvirt/install-missing-file.patch | 12 -
> recipes-extended/libvirt/libvirt/runptest.patch| 34 +++--
> .../libvirt/{libvirt_1.3.2.bb => libvirt_1.3.5.bb} | 10 ++--
> 7 files changed, 47 insertions(+), 87 deletions(-)
> rename recipes-extended/libvirt/{libvirt-1.3.2 =>
> libvirt-1.3.5}/0001-to-fix-build-error.patch (100%)
> delete mode 100644
> recipes-extended/libvirt/libvirt/0001-fix-crash-in-getAllDomainStats.patch
> rename recipes-extended/libvirt/{libvirt_1.3.2.bb => libvirt_1.3.5.bb}
> (97%)
>
> diff --git
> a/recipes-extended/libvirt/libvirt-1.3.2/0001-to-fix-build-error.patch
> b/recipes-extended/libvirt/libvirt-1.3.5/0001-to-fix-build-error.patch
> similarity index 100%
> rename from
> recipes-extended/libvirt/libvirt-1.3.2/0001-to-fix-build-error.patch
> rename to
> recipes-extended/libvirt/libvirt-1.3.5/0001-to-fix-build-error.patch
> diff --git a/recipes-extended/libvirt/libvirt-python.inc
> b/recipes-extended/libvirt/libvirt-python.inc
> index 405d5f7..7fcce43 100644
> --- a/recipes-extended/libvirt/libvirt-python.inc
> +++ b/recipes-extended/libvirt/libvirt-python.inc
> @@ -17,10 +17,9 @@ FILES_${PN}-python = "${bindir}/* ${libdir}/*
> ${libdir}/${PYTHON_DIR}/*"
>
> SRC_URI += "
> http://libvirt.org/sources/python/libvirt-python-${PV}.tar.gz;name=libvirt_python
> "
> SRC_URI +=
> "file://libvirt_api_xml_path.patch;patchdir=../libvirt-python-${PV}"
> -SRC_URI +=
> "file://0001-fix-crash-in-getAllDomainStats.patch;patchdir=../libvirt-python-${PV}"
>
> -SRC_URI[libvirt_python.md5sum] = "ed018c714d7ddbe93221c796dff283ed"
> -SRC_URI[libvirt_python.sha256sum] =
> "6d35ae9e7801573393b9c92471f39e6700d479f10b641df81d041b469f160bf8"
> +SRC_URI[libvirt_python.md5sum] = "4dbd7ef9ee9c4dea5887b5b31eb04529"
> +SRC_URI[libvirt_python.sha256sum] =
> "a0508a57637fd18a3584fb9d2322fb172f65708c9db16e0438a70eb0f36fa5c2"
>
> export LIBVIRT_API_PATH = "${S}/docs/libvirt-api.xml"
> export LIBVIRT_CFLAGS = "-I${S}/include"
> diff --git
> a/recipes-extended/libvirt/libvirt/0001-fix-crash-in-getAllDomainStats.patch
> b/recipes-extended/libvirt/libvirt/0001-fix-crash-in-getAllDomainStats.patch
> deleted file mode 100644
> index 0583a94..000
> ---
> a/recipes-extended/libvirt/libvirt/0001-fix-crash-in-getAllDomainStats.patch
> +++ /dev/null
> @@ -1,57 +0,0 @@
> -From e9c4e2abffef007a28112ebb40a9586b0128f10b Mon Sep 17 00:00:00 2001
> -From: Pavel Hrdina
> -Date: Mon, 18 Apr 2016 16:53:50 +0200
> -Subject: [PATCH] fix crash in getAllDomainStats
> -
> -Upstream-Status: Backport
> -
> -Commits 1d39dbaf and 827ed9b4 broke the libvirt-python API by removing
> -virDomainRef() and virDomainFree(). virDomainStatsRecordListFree() will
> -free that domain pointer and later when virDomain (python object) call
> -its destructor and tries to free that same pointer again.
> -
> -Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1326839
> -
> -Signed-off-by: Pavel Hrdina
>
> - libvirt-override.c | 8 +++-
> - 1 file changed, 7 insertions(+), 1 deletion(-)
> -
> -diff --git a/libvirt-override.c b/libvirt-override.c
> -index 4640ed5..2de95ce 100644
> a/libvirt-override.c
> -+++ b/libvirt-override.c
> -@@ -8381,6 +8381,7 @@ convertDomainStatsRecord(virDomainStatsRecordPtr
> *records,
> - PyObject *py_retval;
> - PyObject *py_record;
> - PyObject *py_record_stats = NULL;
> -+virDomainPtr dom = NULL;
> - size_t i;
> -
> - if (!(py_retval = PyList_New(nrecords)))
> -@@ -8392,9 +8393,12 @@ convertDomainStatsRecord(virDomainStatsRecordPtr
> *records,
> -
> - VIR_PY_LIST_SET_GOTO(py_retval, i, py_record, error);
> -
> -+dom = records[i]->dom;
> -+virDomainRef(dom);
> - VIR_PY_TUPLE_SET_GOTO(py_record, 0,
> -- libvirt_virDomainPtrWrap(records[i]->dom),
> -+ libvirt_virDomainPtrWrap(dom),
> - error);
> -+dom = NULL;
> -
> - if (!(py_record_stats =
> getPyVirTypedParameter(records[i]->params,
> -
> records[i]->nparams)))
> -@@ -8406,6 +8410,8 @@ convertDomainStatsRecord(virDomainStatsRecordPtr
> *records,
>
Re: [yocto] Layer priorities & package selection
On 8/4/16 12:28 AM, Gujulan Elango, Hari Prasath (H.) wrote: > Hello all, > > > We are having two yocto layers in our project. One is SoC specific layer > and the other is the meta-ivi. Now we have two packages provided by both > these layers. wayland_1.9.0 & weston_1.9.0. We want both these packages > from the SoC specific layer and not the ones that are coming from > meta-ivi. The reason being that the SoC vendor has done some > modifications for hw acceleration and stuff like that. Since meta-ivi is > having higher priority( Priority: 7) than the SoC specific > layer(Priority : 6) , naturally these packages are provided by meta-ivi > and not the Soc layer which we actually want. > > > How to modify the layer priority without touching the layer specific > conf file ? Can we have a append to the layer conf file ? bbappends only work for recipe metadata not for config metadate space, so no it wont be possible. You might BBMASK off the meta-ivi recipes. ideally, its better if SOC layers append to such recipes from common layers. So you might want to see if that is doable with your SOC layer then you should propose a patch for your SOC layer to do so. > > > > _meta-ivi:_ > > [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$ > find . -name "wayland*" > ./meta-ivi/recipes-graphics/wayland > ./meta-ivi/recipes-graphics/wayland/wayland_1.9.0.bb > > > [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-ivi$ > find . -name "weston*" > ./meta-ivi/recipes-graphics/wayland/weston > ./meta-ivi/recipes-graphics/wayland/weston/weston.png > ./meta-ivi/recipes-graphics/wayland/weston/weston.desktop > ./meta-ivi/recipes-graphics/wayland/weston_1.9.0.bb > ./meta-ivi/recipes-graphics/wayland/weston_1.9.0.bbappend > ./meta-ivi-bsp/recipes-graphics/weston > > > > _meta-renesas:_ > > > > [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$ > find . -name "wayland*" > ./meta-rcar-gen3/recipes-graphics/wayland > ./meta-rcar-gen3/recipes-graphics/wayland/wayland_1.9.0.bb > > > > [mailto:hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$]hgujulan@chipd010:~/project/monarch/release_testing/monarch-1.2.0/monarch-distribution/meta-renesas$ > find . -name "weston*" > ./meta-rcar-gen3/recipes-graphics/wayland/weston.inc > ./meta-rcar-gen3/recipes-graphics/wayland/weston-init.bbappend > ./meta-rcar-gen3/recipes-graphics/wayland/weston > ./meta-rcar-gen3/recipes-graphics/wayland/weston/weston.png > ./meta-rcar-gen3/recipes-graphics/wayland/weston/weston.desktop > ./meta-rcar-gen3/recipes-graphics/wayland/weston_%.bbappend > ./meta-rcar-gen3/recipes-graphics/wayland/weston-init > ./meta-rcar-gen3/recipes-graphics/wayland/weston-init/weston.service > ./meta-rcar-gen3/recipes-graphics/wayland/weston_1.9.0.bb > ./meta-rcar-gen3/recipes-graphics/wayland/weston_1.9.0.bbappend > > > > Thanks & Regards, > > Hari Prasath > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [GIT PULL | BXT-REBASE] USB Perihperal RTPM fixes
On Thu, Aug 4, 2016 at 11:52 AM, Kumar, Anil K wrote: > > > Anil K Kumar, PhD > Principal Engineer > Lead System Architect > Makers & Innovators Group (MIG) / New Technology Group (NTG) > A clean resend would have been better, since this history comes through somewhat mangled with a forward like this. > > > -Original Message- > From: Wold, Saul > Sent: Thursday, August 4, 2016 8:41 AM > To: Kumar, Anil K ; Felipe Balbi < > felipe.ba...@linux.intel.com>; Ashfield, Bruce (Wind River) < > bruce.ashfi...@windriver.com> > Cc: Renganathan, Prabu ; Svahn, Kai < > kai.sv...@intel.com>; Ponnusamy, Siva Prasath < > siva.prasath.ponnus...@intel.com>; Hart, Patrick J < > patrick.j.h...@intel.com>; Leblanc, Darrell ; > yocto@yoctoproject.org > Subject: Re: [GIT PULL | BXT-REBASE] USB Perihperal RTPM fixes > > > These requests need to go to the linux-yo...@yoctoproject.org list. > This is part of the open source process and needs to be followed for > transparency. > > Sending it to me or directly to Bruce will not work. > > Also, please understand that Bruce is on vacation this week, he will merge > things time permitting, but his gmail email must also be CC'ed otherwise he > may not see it. (bruce.ashfi...@gmail.com). > > > Sau! > > > On Thu, 2016-08-04 at 07:37 -0700, Kumar, Anil K wrote: > > + Saul > > > > Anil K Kumar, PhD > > Principal Engineer > > Lead System Architect > > Makers & Innovators Group (MIG) / New Technology Group (NTG) > > > > > > -Original Message- > > From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com] > > Sent: Thursday, August 4, 2016 4:34 AM > > To: Ashfield, Bruce (Wind River) > > Cc: Kumar, Anil K ; Renganathan, Prabu > .renganat...@intel.com>; Svahn, Kai ; Ponnusamy, > > Siva Prasath ; Hart, Patrick J > rick.j.h...@intel.com>; Leblanc, Darrell ; > > yocto@yoctoproject.org > > Subject: [GIT PULL | BXT-REBASE] USB Perihperal RTPM fixes > > > > > > Hi Bruce, > > > > please pull following branch and apply on top of bxt-rebase. It fixes > > a few issues with runtime PM with drivers/usb/dwc3/ > > > But I was able to pick up the pull request from here and do the merge. Cheers, Bruce > > Best > > > > The following changes since commit > > 17a1643e70318316c4cd275d1c1f252d0a97f46f: > > > > Merge branch 'standard/intel/base' into standard/intel/bxt-rebase > > (2016-07-25 23:56:53 -0400) > > > > are available in the git repository at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git bxt- > > testing-pm > > > > for you to fetch changes up to > > fea0e55419272d6185c1d19a1a5b89e0545cbc39: > > > > usb: dwc3: pci: call _DSM for suspend/resume (2016-08-04 09:35:44 > > +0300) > > > > > > Felipe Balbi (5): > > usb: dwc3: pci: runtime_resume child device > > usb: dwc3: core: allow device to runtime_suspend several times > > usb: dwc3: gadget: increment request->actual once > > usb: dwc3: make sure UX_EXIT_PX is cleared > > usb: dwc3: pci: call _DSM for suspend/resume > > > > drivers/usb/dwc3/core.c | 7 +++ > > drivers/usb/dwc3/core.h | 1 + > > drivers/usb/dwc3/dwc3-pci.c | 105 > > +--- > > drivers/usb/dwc3/gadget.c | 19 > > 4 files changed, 107 insertions(+), 25 deletions(-) > > > > > > -- > > balbi > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] where to find license files?
On 8/4/16 10:32 AM, Gary Thomas wrote: > On 2016-08-04 18:47, Fred Ollinger wrote: >> I'm working on getting a list of license files and I don't know where >> to get the exact text of each license. >> >> Is there a place where this is provided by yocto? >> >> For example, is there some directory which has all the license files? >> >> I see there's an md5sum for each file so I assume this is the case. > > After you build an image, look in /tmp/deploy/licenses/* > > These are the exact licenses used by your image > You may not be able to say exact since, in some cases, it will copy a template text of a given license from common templates. so you should inspect them manually. see the image license manifest and determine which all packages made into your image and review each one of them -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
