Re: [yocto] How to patch a driver in Linux source tree

Hi Jeremy, I understand most of what you've got here, thanks, but I'm confused on the SRC_URI="…". Where should I look for the kernel git directory? I'm running Yocto with a mirror directory and that contains git directories for all of the major pieces, but I don't see one for the kernel. The

[yocto] Problem with Extensible SDK update

Hi, I am trying to update an installation of the Yocto Extensible SDK by running: devtool sdk-update update-url Now it seems like the devtool program is not doing any error checking other than verifying whether "update-url" contains a "://" sequence. Whatever random URL I throw at it, it just

Re: [yocto] How to patch a driver in Linux source tree

SRC_URI = " file://your-patch-path" Then place the patch in files subdirectory. So your tree should look something like: /recipes-kernel/linux/ linux-raspberrypi_4.4.bbappend files/ Instead of "files", it might be named "linux-raspberrypi". Hope this helps, Jeremy On Fri, Apr 13,

Re: [yocto] Regarding support of machine learning algorithm/framework

On 04/12/2018 06:19 AM, atulkumar singh wrote: These days we are hearing a lot about artificial intelligence and now every company whichever domain it belongs works in AI. Either it's about automotive(Autonomous driving), Surveillance(Object detection) or IOT. So as the industry is moving

[yocto] How to patch a driver in Linux source tree

I'm working on a raspberry pi3 Yocto build from Qt's boot2qt project, it's running Yocto version 2.2.3, and Linux kernel 4.4.50. I need to back port some changes to a file in drivers/net/can/spi. I confused about where and how I set up the patch file. I have a linux-raspberrypi_4.4.bbappend

[yocto] [meta-qt4][v2][PATCH 1/2] layer: add LAYERSERIES_COMPAT

[v2] use the real layer name Signed-off-by: Armin Kuster --- conf/layer.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/layer.conf b/conf/layer.conf index 62ce9cc..1ce54af 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -8,3 +8,4 @@ BBFILE_COLLECTIONS +=

Re: [yocto] [meta-qt3][PATCH 1/2] layer: add LAYERSERIES_COMPAT

On Fri, Apr 13, 2018 at 03:41:26PM -0700, Armin Kuster wrote: > Signed-off-by: Armin Kuster > --- > conf/layer.conf | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/conf/layer.conf b/conf/layer.conf > index 84ab5f7..2100ffb 100644 > --- a/conf/layer.conf > +++

Re: [yocto] [meta-qt3][PATCH 1/2] layer: add LAYERSERIES_COMPAT

On 04/13/2018 03:44 PM, Martin Jansa wrote: > On Fri, Apr 13, 2018 at 03:41:26PM -0700, Armin Kuster wrote: >> Signed-off-by: Armin Kuster >> --- >> conf/layer.conf | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/conf/layer.conf b/conf/layer.conf >> index

[yocto] [meta-selinux][PATCH] layer: add LAYERSERIES_COMPAT for sumo

Signed-off-by: Armin Kuster --- conf/layer.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/layer.conf b/conf/layer.conf index b13633a..0f9ea41 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -18,6 +18,8 @@ BBFILE_PRIORITY_selinux = "5" # cause

[yocto] [meta-qt3][v2][PATCH 1/2] layer: add LAYERSERIES_COMPAT

[v2] Fix type in name Signed-off-by: Armin Kuster --- conf/layer.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/layer.conf b/conf/layer.conf index 84ab5f7..0197197 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -8,3 +8,4 @@ BBFILE_COLLECTIONS += "qt3"

Re: [yocto] How to patch a driver in Linux source tree

On 4/13/18 11:41 AM, Greg Wilson-Lindberg wrote: I'm working on a raspberry pi3 Yocto build from Qt's boot2qt project, it's running Yocto version 2.2.3, and Linux kernel 4.4.50. I need to back port some changes to a file in drivers/net/can/spi. I confused about where and how I set up the

[yocto] [meta-qt4][PATCH 2/2] layers: move LAYERSERIES_COMPAT to sumo

Signed-off-by: Armin Kuster --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 2fbfad7..67ab5d6 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -8,4 +8,4 @@ BBFILE_COLLECTIONS += "qt4-layer"

[yocto] [meta-qt4][PATCH 1/2] layer: add LAYERSERIES_COMPAT

Signed-off-by: Armin Kuster --- conf/layer.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/layer.conf b/conf/layer.conf index 62ce9cc..2fbfad7 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -8,3 +8,4 @@ BBFILE_COLLECTIONS += "qt4-layer"

[yocto] [meta-qt4][v2][PATCH 2/2] layers: move LAYERSERIES_COMPAT to sumo

[v2] Fix cut error Signed-off-by: Armin Kuster --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 1ce54af..915d89c 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -8,4 +8,4 @@

[yocto] [meta-qt3][PATCH 1/2] layer: add LAYERSERIES_COMPAT

Signed-off-by: Armin Kuster --- conf/layer.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/layer.conf b/conf/layer.conf index 84ab5f7..2100ffb 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -8,3 +8,4 @@ BBFILE_COLLECTIONS += "qt3" BBFILE_PATTERN_qt3 =

[yocto] [meta-qt3][PATCH 2/2] layer: Change LAYERSERIES_COMPAT to sumo

Signed-off-by: Armin Kuster --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 2100ffb..04025ac 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -8,4 +8,4 @@ BBFILE_COLLECTIONS += "qt3"

[yocto] [meta-qt3][v2][PATCH 2/2] layer: Change LAYERSERIES_COMPAT to sumo

[v2] fix typo in layer name Signed-off-by: Armin Kuster --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 0197197..cfcad24 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -8,4 +8,4 @@

[yocto] How to set MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS under my custom layer

Hi all, I am trying to add kernel modules to rootfs. I tried adding configuration MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS_append = " kernel-module-module1" into .conf is OK, module1 get installed. I also tried adding same configuration into build/conf/local.conf also OK, module1 get installed. But

[yocto] [meta-selinux][PATCH 1/3] libselinux: refresh patches to fix QA warning

Refresh patches with devtool command to fix do_patch warning. Signed-off-by: Yi Zhao --- ...c-Makefile-fix-includedir-in-libselinux.pc.patch | 14 ++ .../libselinux-define-FD_CLOEXEC-as-necessary.patch | 14 ++

Re: [yocto] Which recipe produce that file?

Hello Mauro, Seems that you have somehow included duplicate recipes for xcb-util, in form of libxcb-util. I found the base package xcb-util in my base: meta (Open Embedded) layer: [user@localhost beaglebone-rocko-18.0.0]$ find . -name xcb-uti* *./meta/recipes-graphics/xorg-lib/xcb-util_0.4.0.bb

Re: [yocto] Which recipe produce that file?

Ok. Thanks for your help MZ Il 13/04/2018 09:49, Zoran Stojsavljevic ha scritto: Hello Mauro, Seems that you have somehow included duplicate recipes for xcb-util, in form of libxcb-util. I found the base package xcb-util in my base: meta (Open Embedded) layer: [user@localhost

Re: [yocto] Getting the version of Yocto that is being used.

Thanks for the help. :) Yes they are Phytec boards. I have inherited the project from a 3rd party and so in the mids of chasing up the support contacts and our account details for their site. I'm sure you've all played the "Q) What are the support / login details? A) I don't know, ask X, ask Y,

[yocto] [meta-selinux][PATCH 3/3] selinux-python: refresh patches to fix QA warning

Refresh patches with devtool command to fix do_patch warning Signed-off-by: Yi Zhao --- .../fix-TypeError-for-seobject.py.patch | 17 + .../selinux-python/fix-sepolicy-install-path.patch | 21 -

[yocto] [meta-selinux][PATCH 2/3] libsemanage: refresh patches to fix QA warning

Refresh patches with devtool command to fix do_patch warning. Signed-off-by: Yi Zhao --- ...rc-Makefile-fix-includedir-in-libselinux.pc.patch | 16 +++- .../libsemanage-Fix-execve-segfaults-on-Ubuntu.patch | 20 +---

Re: [yocto] [meta-mingw][PATCH] qemu_2.11.%.bbappend: fix broken qemu build for mingw

Thanks Juro. I'll remember to keep an eye out for the ifdefs disappearing. Ross On 13 April 2018 at 15:46, Bystricky, Juro wrote: > yes, I've done it before: > https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=sumo=bc112b8368eb3842ccb2430fdf17e736ea39a742 >

[yocto] Question about automatic dependencies when native packages are used

I'm having some trouble with native dependencies in my recipe, and I'm wondering if anyone has any tips. I'm building with the petalinux toolset on an x64 linux for an arm architecture. I have a recipe myapp, which has a native version, myapp-native. myapp depends on its myapp-native, as

Re: [yocto] Yocto Boot Question

I also faced a similar issue while installing on Intel machine, switching to other machine I was able to install and boot successfully.. I have not tried network boot option.. Which is the board you are using and what is the machine type? Regards, Jamal From: yocto-boun...@yoctoproject.org

[yocto] Regarding support of machine learning algorithm/framework

Hello All, These days we are hearing a lot about artificial intelligence and now every company whichever domain it belongs works in AI. Either it's about automotive(Autonomous driving), Surveillance(Object detection) or IOT. So as the industry is moving towards AI, in that case, is there

[yocto] Devtool: Different binaries with and without devtool

Hi, using poky 2.4.1. When building our custom linux kernel recipe with a fixed git hash for SRCREV, compared to building it after "devtool modify --no-extract" with the same hash checked out, we get different binaries and the later doesn't boot. This is our normal workflow and have worked fine

Re: [yocto] [meta-mingw][PATCH] qemu_2.11.%.bbappend: fix broken qemu build for mingw

On Fri, Apr 13, 2018 at 8:19 AM, Burton, Ross wrote: > Thanks Juro. I'll remember to keep an eye out for the ifdefs disappearing. Maybe add some comments in the patch to ensure whoever is working with it knows why they are there. Alistair > > Ross > > On 13 April 2018

Re: [yocto] Question about automatic dependencies when native packages are used

On 10 April 2018 at 18:49, Aaron M. Biver wrote: > The problem that myapp-native is trying to include mymodule-native. This > complains: Just make the dependency on mymodule target-specific. Lots of ways depending on what the dependencies are. Either clear the native

Re: [yocto] [meta-mingw][PATCH] qemu_2.11.%.bbappend: fix broken qemu build for mingw

Is it feasible to fix the original patch? Ross On 13 April 2018 at 00:55, Juro Bystricky wrote: > The commit "qemu: Bump to version 2.11.0" in oe-core broke the > build of qemu for mingw, due to using "socketpair", which is > not supported by mingw. "socketpair" is

Re: [yocto] Which recipe produce that file?

Toradex Qt5 complete set of layers for Colibri iMX6board (I did it in 09/2017 and implated it on Toradex development board): This version is meta-toolchain-qt5 + angstrom-lxde-image (Qt5 + LXDE DT with X11 server): [user@localhost Qt5-plus-x11]$ cd oe-core [user@localhost oe-core]$ ls -al total

Re: [yocto] Getting the version of Yocto that is being used.

Hello Richard, some of us are also around on the list. You should find all documentation on the product page. Specifically, the git tag of the release is "2.2.1-phy3" which indicates that the release bundles poky morty 2.2.1. In future we will also have LAYERSERIES_COMPAT set. If the

Re: [yocto] [meta-mingw][PATCH] qemu_2.11.%.bbappend: fix broken qemu build for mingw

yes, I've done it before: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=sumo=bc112b8368eb3842ccb2430fdf17e736ea39a742 I'll do it gain. Hopefully it will last longer this time. From: Burton, Ross [ross.bur...@intel.com] Sent: Friday, April 13,

Re: [yocto] Getting the version of Yocto that is being used.

Hello Ross, I have a different idea for poky versioning. Since, who ever does classical poky, one will have at least three layers there from your reference poky distro: --- Build Configuration: | --- DISTRO = poky DISTRO_VERSION = 2.4