Re: [yocto] Migrate, or not Migrate, that's the question!!!

2016-02-02 Thread Diego Sueiro 
Khem,

On 1 February 2016 at 18:34, Khem Raj  wrote:

>
> I think you have to think about what you are getting into. You are trying
> to mix quite two different things are create third one. If I were you, I
> would just
> keep myself synced with upstream as much as I could, Don’t look one way,
> you have to look into time and effort you will spend on maintaining this new
> jargon for years to come.
>

Thanks for your opinion.

I agree with you, but this decision is out of my responsibility.

We already had problems on backporting device drivers and packages.
I believe that for the next generation of the product we'll try to keep
synced with upstream, but until then I want to try to use a recent version
of Yocto/OE.


Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br


/*long live rock 'n roll*/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Migrate, or not Migrate, that's the question!!!

2016-02-02 Thread Diego Sueiro 
On 2 February 2016 at 08:40, Diego Sueiro  wrote:

> Khem,
>
> On 1 February 2016 at 18:34, Khem Raj  wrote:
>
>>
>> I think you have to think about what you are getting into. You are trying
>> to mix quite two different things are create third one. If I were you, I
>> would just
>> keep myself synced with upstream as much as I could, Don’t look one way,
>> you have to look into time and effort you will spend on maintaining this new
>> jargon for years to come.
>>
>
> Thanks for your opinion.
>
> I agree with you, but this decision is out of my responsibility.
>
> We already had problems on backporting device drivers and packages.
> I believe that for the next generation of the product we'll try to keep
> synced with upstream, but until then I want to try to use a recent version
> of Yocto/OE
>


And just to keep it clear. We are talking about a project with 272 packages
and 1.5 MLOC (proprietary embedded code) which took 4 years to be developed.


Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br


/*long live rock 'n roll*/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] network drivers are not installed when MACHINE qemux86-64

2016-02-02 Thread Nathan Sowatskey 
Hi Khem

Thanks for following up. I am very new to Yocto, so I am probably missing some 
context around your question.

For example, I don’t know what the “relevant kernel modules” would be, and I 
don’t know where MACHINE_EXTRA_RECOMMENDS is defined.

I don’t see the MACHINE_EXTRA_RECOMMENDS variable in any file in build/conf, 
nor in the environment variables.

Regards

Nathan

> On 2 Feb 2016, at 06:05, Khem Raj  wrote:
> 
> On Mon, Feb 1, 2016 at 8:48 PM, Nathan Sowatskey  wrote:
>> As a follow up, I have just done this:
>> 
>> bitbake core-image-kernel-dev
>> 
>> And now I get the eth0 interface configured and active when I start the 
>> Yocto image.
>> 
>> I do not have to configure and start it manually.
> 
> Can you check if relevant kernel modules are listed in 
> MACHINE_EXTRA_RRECOMMENDS
> 
>> 
>> Regards
>> 
>> Nathan
>> 
>>> On 1 Feb 2016, at 13:31, Nathan Sowatskey  wrote:
>>> 
>>> Hi
>>> 
>>> I think I am seeing something similar. I only have video in my 
>>> kernel/drivers directory, which is to say that there is no net directory 
>>> either.
>>> 
>>> I have been using the Build Appliance to create a qemux86-64 
>>> core-image-full-cmdline machine. When I ran that without any -netdev 
>>> arguments at all, on OSX, I was able to use -redir tcp:::22 to enable 
>>> SSH from the host.
>>> 
>>> At least, that did work a few times at least last week.
>>> 
>>> Now, I have to manually edit the /etc/network/interfaces file to add iface 
>>> eth0 init dhcp, and then manually ifup eth0.
>>> 
>>> I am sure I did not have to do that with builds last week.
>>> 
>>> Regards
>>> 
>>> Nathan
>>> 
 On 29 Jan 2016, at 21:59, Alexandre Freire da Silva Osorio 
  wrote:
 
 You’re right, Ross. They’re present in modules-qemux86-64.tgz. The problem 
 is that for some reason the drivers are not being copied to the root 
 filesystem.
 
 For example, the expected 
 lib/modules/3.14.36ltsi-yocto-standard/kernel/drivers/net/ directory is 
 not created in the rootfs.
 
 Thanks.
 
 Alexandre
 
 From: Burton, Ross [mailto:ross.bur...@intel.com]
 Sent: sexta-feira, 29 de janeiro de 2016 18:52
 To: Alexandre Freire da Silva Osorio 
 Cc: yocto@yoctoproject.org
 Subject: Re: [yocto] network drivers are not installed when MACHINE 
 qemux86-64
 
 
 On 29 January 2016 at 18:41, Alexandre Freire da Silva Osorio 
  wrote:
 When I build a core-image-lsb image for MACHINE qemux86-64, the network 
 drivers are not enabled. When building the same image for genericx86-64, 
 this problem doesn’t occur and all the drivers are enabled.
 
 qemux86-64 certainly ships with network drivers for the qemu machine.  
 What drivers are you expecting to be present?
 
 Ross
 --
 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto
>>> 
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>> 
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto

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

[yocto] How to build for various boards from one yocto installation

2016-02-02 Thread Marius 
I have a custom board (similar to BBB) that has no HDMI and no network 
as well as a standard BBB. I want to build images for each from my yocto 
(poky-jethro) installation.

Can it be done and if so how do I go about that?

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

[yocto] [meta-raspberrypi][PATCH 3/3] linux-raspberrypi: use STAGING_LIBEXECDIR_NATIVE for rpi-mkimage tools

2016-02-02 Thread Maciej Borzecki 
The rpi-mkimage tools are installed ${libexecdir}/rpi-mkimage within
native sysroot, where ${libexecdir} resolves to /usr/libexec. This caused
the build to fail due to recipe trying to access ${libdir}/mkimage. Fix
the paths to use an unambiguous STAGING_LIBEXECDIR_NATIVE so that a
proper location is used.

Signed-off-by: Maciej Borzecki 
---
 recipes-kernel/linux/linux-raspberrypi.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc
index 
70e8bfebba75e29e55c8b48856fa51d74e586612..05f2d2b2957384667383e5f865ccfb487121e641
 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -60,7 +60,7 @@ do_rpiboot_mkimage() {
 if test "x${KERNEL_IMAGETYPE}" != "xuImage" ; then
 if test -n "${KERNEL_DEVICETREE}"; then
 # Add RPi bootloader trailer to kernel image to enable DeviceTree 
support
-${STAGING_DIR_NATIVE}/usr/lib/rpi-mkimage/mkknlimg --dtok 
${KERNEL_OUTPUT} ${KERNEL_OUTPUT}
+${STAGING_LIBEXECDIR_NATIVE}/rpi-mkimage/mkknlimg --dtok 
${KERNEL_OUTPUT} ${KERNEL_OUTPUT}
 fi
 fi
 }
-- 
2.5.0

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

[yocto] [meta-raspberrypi][PATCH 0/3] libexecdir fixes

2016-02-02 Thread Maciej Borzecki 
A couple of fixes that resolve issues with recent change of libexecdir
in OE-core.

The first patch cleans up the recipe to install rpi-mkimage tools into
${libexecdir}/rpi-mkimage. This preserves the original nesting of
rpi-mkimage under ${libdir}.

The 2nd and 3rd patch use ${STAGING_LIBEXECDIR_NATIVE} rather than a mix
of ${STAGING_DIR_NATIVE}${libexecdir} to keep things clean.

Maciej Borzecki (3):
  rpi-mkimage: install tools under {libexecdir}/rpi-mkimage
  u-boot-rpi: use STAGING_LIBEXECDIR_NATIVE for rpi-mkimage tools
  linux-raspberrypi: use STAGING_LIBEXECDIR_NATIVE for rpi-mkimage tools

 recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb | 4 ++--
 recipes-bsp/u-boot/u-boot-rpi_git.bb   | 2 +-
 recipes-kernel/linux/linux-raspberrypi.inc | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

--
2.5.0

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

[yocto] [meta-raspberrypi][PATCH 1/3] rpi-mkimage: install tools under {libexecdir}/rpi-mkimage

2016-02-02 Thread Maciej Borzecki 
For consistency with other recipes that look for mkimage
tools (u-boot-rpi, linux-raspberrypi) under ${libexecdir}/rpi-mkimage,
make sure that the tools are installed at the proper location.

Signed-off-by: Maciej Borzecki 
---
 recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb 
b/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
index 
ffcaa83683fd270cb2216b118a3f5be941cfdb89..2c8ecb173c804302ac6e13d4ae7af8ba35bccd26
 100644
--- a/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
+++ b/recipes-bsp/rpi-mkimage/rpi-mkimage_git.bb
@@ -15,8 +15,8 @@ SRC_URI = " \
 S = "${WORKDIR}/git"
 
 do_install () {
-install -d ${D}${libexecdir}
-cp ./mkimage/* ${D}${libexecdir}
+install -d ${D}${libexecdir}/rpi-mkimage
+install -t ${D}${libexecdir}/rpi-mkimage ./mkimage/*
 }
 
 BBCLASSEXTEND = "native"
-- 
2.5.0

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

[yocto] [meta-raspberrypi][PATCH 2/3] u-boot-rpi: use STAGING_LIBEXECDIR_NATIVE for rpi-mkimage tools

2016-02-02 Thread Maciej Borzecki 
The rpi-mkimage tools are installed ${libexecdir}/rpi-mkimage within
native sysroot, where ${libexecdir} resolves to /usr/libexec. This caused
the build to fail due to recipe trying to access ${libdir}/mkimage. Fix
the paths to use an unambiguous STAGING_LIBEXECDIR_NATIVE so that a
proper location is used.

Signed-off-by: Maciej Borzecki 
---
 recipes-bsp/u-boot/u-boot-rpi_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/u-boot/u-boot-rpi_git.bb 
b/recipes-bsp/u-boot/u-boot-rpi_git.bb
index 
db5ea84fc0408d90ccb17ed578305ce5b11f568b..ea0c173b59290d5d6d080c9b487be8bf789f0d58
 100644
--- a/recipes-bsp/u-boot/u-boot-rpi_git.bb
+++ b/recipes-bsp/u-boot/u-boot-rpi_git.bb
@@ -24,6 +24,6 @@ COMPATIBLE_MACHINE = "raspberrypi"
 
 do_compile_append() {
 # Create kernel.img from uboot.bin and name it u-boot.img
-${STAGING_DIR_NATIVE}/usr/lib/rpi-mkimage/imagetool-uncompressed.py 
u-boot.bin
+${STAGING_LIBEXECDIR_NATIVE}/rpi-mkimage/imagetool-uncompressed.py 
u-boot.bin
 mv kernel.img u-boot.img
 }
-- 
2.5.0

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

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Feb. 2, 2016 8:00 AM US Pacific Time

2016-02-02 Thread Jolley, Stephen K 
Attendees: Armin, Stephen, Joshua, Belen, Sona, Richard, Ross,



AR: Armin - Develop a bugzilla enhancement request to handle patches for older 
stable branches.



Agenda:



* Opens collection - 5 min (Stephen)

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

YP 2.1 M2 rc1 is in QA.  Should be out soon.

YP 2.0.1 rc2 came out of QA, but because we had CVE's after it went in, and a 
number of issues.  We will do an rc3 as soon as we can get fixes ready.

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

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

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

* Opens - 10 min

Armin - Discussed change process for patches for older stable branches.

Richard - Python expansion changes are being discussed on the architecture 
list.  Theses might break something.  But after the changes are made we will 
fix them. Overall we think this will fix other important issues.

Richard - Change are being discussed to make files options.  It might also 
break something, but it fixes a number of long term issues.

* Team Sharing - 10 min - Nothing.




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] Problem installing ath10k firmware

2016-02-02 Thread Fred Ollinger 
http://linuxwireless.org/en/users/Drivers/ath10k/firmware/

Seems like you should get the firmware here:

https://github.com/kvalo/ath10k-firmware/tree/master/

and copy it here:

 $ cp firmware-2.bin_10.1.467.2-1 
/lib/firmware/ath10k/QCA988X/hw2.0/firmware-2.bin

Frederick

From: yocto-boun...@yoctoproject.org  on behalf 
of Todd Efflam 
Sent: Monday, February 1, 2016 5:14 PM
To: yocto@yoctoproject.org
Subject: [yocto] Problem installing ath10k firmware

Hello,
We're having a problem getting the ath10k firmware to run with a new
wireless card.  The card uses chip QCA9882.  We've tried installing
ath10k firmware using:
IMAGE_INSTALL_append += linux-firmware-ath10k

in combination with the following kernel configs:
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"

we tried adding
CONFIG_EXTRA_FIRMWARE="ath10k/QCA988X/hw2.0/firmware-2.bin
ath10k/QCA988X/hw2.0/board.bin" but this failed as it wasn't able to
locate the files.

After building, we receive the following error when booting our cpu:
ath10k: Could not fetch firmware file 'firmware-2.bin': -2

We then realized lib/firmware contained firmware-4.bin and
firmware-5.bin instead of firmware-2.bin, but after copying
firmware-4.bin to 2 we still received the same error from our cpu.

Has anyone had success getting ath10k to run with firmware-2.bin?  Any
help would be appreciated!

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

[yocto] [meta-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set

2016-02-02 Thread GUEYTAT Julien 
Hi,

It seems that there are some stiff missing between meta-qt5 or meta-raspberrypi.
When we set the option gles... to qtbase we don't get the QMAKE_LIBS_EGL set 
properly.
We can compare a working set of variables in the qt mkspecs directory of qt.
There is one dedicated file for the RaspberryPi2. May be one also for 
RaspberryPi.
Anyway!
How could we set those *_EGL variables properly? And... If they are properly 
set, will qtbase will take them into account?

I will be happy to propose a patch but I need to get more precision first.
Thanks in advance,



Julien GUEYTAT
Ingénieur Informatique
[Logo CDS SOFT]
1027, avenue du Docteur Julien Lefebre BP27
06271 Villeneuve-Loubet Cedex
Fixe :  +33 (0) 492 024 545
Mob :  +33(0) 617 980 383
Fax :+33(0) 492 024 546
Email : j.guey...@cdssoft.studiel.fr
www : www.studiel.fr
P Pensez Environnement, imprimez seulement si nécessaire

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

[yocto] [meta-raspberrypi][PATCH v3 1/2] qt5: fixed raspberrypi support

2016-02-02 Thread John Madieu 
Because EGL properties were not defined properly, we always had the 
following error
make: *** [egl] Error 1
| EGL disabled.
|  The EGL functionality test failed; EGL is required by some QPA 
plugins to manage cont
|  You might need to modify the include and library search paths by 
editing QMAKE_INCDIR

x11 in DISTRO_FEATURES also produced the following error
error: 'QAccessible' has not been declared
|  } else if 
(QStyleHelper::isInstanceOf(groupBox->styleObject,
QAccessible::Grouping)) {
|   ^
|Makefile:53048: recipe for target '.obj/qgtkstyle.o' failed

This bbappend definitively fix these bug

Signed-off-by: John Madieu 
---
 qt5-layer/recipes-qt/qt5/qtbase_%.bbappend | 33 ++
 1 file changed, 33 insertions(+)
 create mode 100644 qt5-layer/recipes-qt/qt5/qtbase_%.bbappend

diff --git a/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend 
b/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend
new file mode 100644
index 000..f61cd1d
--- /dev/null
+++ b/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend
@@ -0,0 +1,33 @@
+
+# Raspberrypi only need gles2
+PACKAGECONFIG_GL = "gles2"
+
+QT_CONFIG_FLAGS_append = "${@base_contains('DISTRO_FEATURES', 'x11', ' 
-accessibility ', '', d)}"
+do_configure_prepend_rpi() {
+
+   sed -i 's!load(qt_config)!!' ${S}/mkspecs/linux-oe-g++/qmake.conf
+if ! grep -q '^EGLFS_' ${S}/mkspecs/linux-oe-g++/qmake.conf; then
+cat >> ${S}/mkspecs/linux-oe-g++/qmake.conf <> ${S}/mkspecs/linux-oe-g++/qmake.conf <> ${S}/mkspecs/linux-oe-g++/qmake.conf <> ${S}/mkspecs/linux-oe-g++/qmake.conf

[yocto] [meta-raspberrypi][PATCH v3 2/2] layer.conf: avoid to force users to add the qt5 layer because of qtbase bbappend

2016-02-02 Thread John Madieu 
Signed-off-by: John Madieu 
---
 conf/layer.conf | 4 
 1 file changed, 4 insertions(+)

diff --git a/conf/layer.conf b/conf/layer.conf
index bea5a65..60f1bcb 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -12,3 +12,7 @@ BBFILE_PRIORITY_raspberrypi = "9"
 # Additional license directories.
 LICENSE_PATH += "${LAYERDIR}/files/custom-licenses"
 
+# Let us add layer-specific (such as qt5-layer) bbappends which
+# are only applied when that layer is included in our configuration
+BBFILES += "${@' '.join('${LAYERDIR}/%s/recipes*/*/*.bbappend' % layer \
+   for layer in BBFILE_COLLECTIONS.split())}"
-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH v3 1/2] qt5: fixed raspberrypi support

2016-02-02 Thread John Madieu 
Because EGL properties were not defined properly, we always had the 
following error
make: *** [egl] Error 1
| EGL disabled.
|  The EGL functionality test failed; EGL is required by some QPA 
plugins to manage cont
|  You might need to modify the include and library search paths by 
editing QMAKE_INCDIR

x11 in DISTRO_FEATURES also produced the following error
error: 'QAccessible' has not been declared
|  } else if 
(QStyleHelper::isInstanceOf(groupBox->styleObject,
QAccessible::Grouping)) {
|   ^
|Makefile:53048: recipe for target '.obj/qgtkstyle.o' failed

This bbappend definitively fix these bug

Signed-off-by: John Madieu 
---
 qt5-layer/recipes-qt/qt5/qtbase_%.bbappend | 33 ++
 1 file changed, 33 insertions(+)
 create mode 100644 qt5-layer/recipes-qt/qt5/qtbase_%.bbappend

diff --git a/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend 
b/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend
new file mode 100644
index 000..f61cd1d
--- /dev/null
+++ b/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend
@@ -0,0 +1,33 @@
+
+# Raspberrypi only need gles2
+PACKAGECONFIG_GL = "gles2"
+
+QT_CONFIG_FLAGS_append = "${@base_contains('DISTRO_FEATURES', 'x11', ' 
-accessibility ', '', d)}"
+do_configure_prepend_rpi() {
+
+   sed -i 's!load(qt_config)!!' ${S}/mkspecs/linux-oe-g++/qmake.conf
+if ! grep -q '^EGLFS_' ${S}/mkspecs/linux-oe-g++/qmake.conf; then
+cat >> ${S}/mkspecs/linux-oe-g++/qmake.conf <> ${S}/mkspecs/linux-oe-g++/qmake.conf <> ${S}/mkspecs/linux-oe-g++/qmake.conf <> ${S}/mkspecs/linux-oe-g++/qmake.conf

[yocto] [meta-raspberrypi][PATCH v3 2/2] layer.conf: avoid to force users to add the qt5 layer because of qtbase bbappend

2016-02-02 Thread John Madieu 
Signed-off-by: John Madieu 
---
 conf/layer.conf | 4 
 1 file changed, 4 insertions(+)

diff --git a/conf/layer.conf b/conf/layer.conf
index bea5a65..60f1bcb 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -12,3 +12,7 @@ BBFILE_PRIORITY_raspberrypi = "9"
 # Additional license directories.
 LICENSE_PATH += "${LAYERDIR}/files/custom-licenses"
 
+# Let us add layer-specific (such as qt5-layer) bbappends which
+# are only applied when that layer is included in our configuration
+BBFILES += "${@' '.join('${LAYERDIR}/%s/recipes*/*/*.bbappend' % layer \
+   for layer in BBFILE_COLLECTIONS.split())}"
-- 
1.9.1

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

Re: [yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Feb. 2, 2016 8:00 AM US Pacific Time

2016-02-02 Thread akuster 


On 02/02/2016 08:19 AM, Jolley, Stephen K wrote:
> Attendees: Armin, Stephen, Joshua, Belen, Sona, Richard, Ross,
> 
> 
> 
> AR: Armin - Develop a bugzilla enhancement request to handle patches for 
> older stable branches.

bug is 9037

- armin
> 
> 
> 
> Agenda:
> 
> 
> 
> * Opens collection - 5 min (Stephen)
> 
> * Yocto Project status - 5 min (Stephen/team)
> 
> YP 2.1 M2 rc1 is in QA.  Should be out soon.
> 
> YP 2.0.1 rc2 came out of QA, but because we had CVE's after it went in, and a 
> number of issues.  We will do an rc3 as soon as we can get fixes ready.
> 
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status
> 
> https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule
> 
> https://wiki.yoctoproject.org/wiki/Yocto_2.1_Features
> 
> * Opens - 10 min
> 
> Armin - Discussed change process for patches for older stable branches.
> 
> Richard - Python expansion changes are being discussed on the architecture 
> list.  Theses might break something.  But after the changes are made we will 
> fix them. Overall we think this will fix other important issues.
> 
> Richard - Change are being discussed to make files options.  It might also 
> break something, but it fixes a number of long term issues.
> 
> * Team Sharing - 10 min - Nothing.
> 
> 
> 
> 
> 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] Problem installing ath10k firmware

2016-02-02 Thread Todd Efflam 
> Seems like you should get the firmware here:
>
> https://github.com/kvalo/ath10k-firmware/tree/master/
>
> and copy it here:
>
>  $ cp firmware-2.bin_10.1.467.2-1 
> /lib/firmware/ath10k/QCA988X/hw2.0/firmware-2.bin

Thanks Fred, we actually tried this but it still fails.

It seems like the two options are to build ath10k as a module, or
built-in.  The thing is we're running into problems with each
approach.

For ath10k as a module, our understanding was to also add
"kernel-module-ath10k" to image_install in addition to changing the
kernel config to m.  The module should then be able to access firmware
in the /lib/firmware/ directory if we push it to the filesystem as
Fred mentioned. This however fails as yocto is unable to find
kernel-module-ath10k (is the naming incorrect?).

For built-in, the approach we were taking was as mentioned in my
initial post.  This should build the firmware into the kernel (using
linux-firmware package) and allow us to not make ath10k a loadable
module, but this fails as well as the kernel is unable to find the
files:
" *** No rule to make target
`/lib/firmware/ath10k/QCA988X/hw2.0/firmware-4.bin', needed by
`firmware/ath10k/QCA988X/hw2.0/firmware-4.bin.gen.o'.  Stop."

We're going to keep trying on both approaches and I'll post back if I
make any progress, but if anyone has any tips/sees any errors in what
we're doing let me know!

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

Re: [yocto] [raspberrypi2] do_rootfs() failure at the end of qt5-image-demo recipe

2016-02-02 Thread Khem Raj 

> On Feb 1, 2016, at 10:53 PM, Karim ATIKI  wrote:
> 
> Hello,
> 
> I'm experiencing issue while building qt-image-demo (jethro) for raspberrypi2.
> At the very end of the build: do_rootfs failure.
> 
> Collected errors:
>  * satisfy_dependencies_for: Cannot satisfy the following dependencies for 
> packagegroup-qt5-graphics:
>  *  qt3d-tools *
>  * opkg_install_cmd: Cannot install package packagegroup-qt5-graphics.
> 
> However, I haven't added or modified the layers and recipes.
> 
> Any idea ?

check if right knobs are enabled in meta-qt5 to enable qt3d-tools. There are 
cases sometimes where DISTRO_FEATURES control
the knobs and that differs from distro to distro

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


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

[yocto] [meta-raspberrypi] errors when I "bitbake" an image for my rpi2 B+ board

2016-02-02 Thread 张健 
[meta-raspberrypi]
Hi,every one. 
I'm trying to use meta-raspberrypi layer to build an image for my raspberrypi2 
B+ board. 


After I download poky,I git clone meta-raspberrypi layer as follows: "git clone 
git://git.yoctoproject.org/meta-raspberrypi"

Then I totally follow the README in the meta-raspberrypi directory as follows:
"
.
How to use it:


1. source poky/oe-init-build-env rpi-build
2. Add needed layer to bblayers.conf:
- meta-raspberrypi
3  Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf  (I set machine to 
be "raspberrypi2" here)
4. bitbake rpi-hwup-image
5. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is used)
6. Boot your RPI.

"


but it comes out with several errors after "bitbake", I don't know why, 
warnings and errors are as follows:
"
WARNING: Failed to fetch URL 
ftp://invisible-island.net/ncurses/current/ncurses-5.9-20150329.tgz, attempting 
MIRRORS if available
WARNING: Failed to fetch URL 
http://kernel.org/pub/linux/kernel/v4.x/linux-4.1.tar.xz, attempting MIRRORS if 
available
ERROR: Fetcher failure: Fetch command failed with exit code 4, output:
wget: unable to resolve host address 'kernel.org'


ERROR: Function failed: Fetcher failure for URL: 
'http://kernel.org/pub/linux/kernel/v4.x/linux-4.1.tar.xz'. Unable to fetch URL 
from any source.
ERROR: Logfile of failure stored in: 
/home/jackzhang1992/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/linux-libc-headers/4.1-r0/temp/log.do_fetch.8031
ERROR: Task 961 
(/home/jackzhang1992/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.1.bb,
 do_fetch) failed with exit code '1'
WARNING: Failed to fetch URL 
http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.12.0.0.tar.xz,
 attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 4, output:
wget: unable to resolve host address 'ymorin.is-a-geek.org'


ERROR: Function failed: Fetcher failure for URL: 
'http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.12.0.0.tar.xz'.
 Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: 
/home/jackzhang1992/poky/build/tmp/work/i686-linux/kconfig-frontends-native/3.12.0.0-r0/temp/log.do_fetch.8067
ERROR: Task 728 
(virtual:native:/home/jackzhang1992/poky/meta/recipes-devtools/kconfig-frontends/kconfig-frontends_3.12.0.0.bb,
 do_fetch) failed with exit code '1'
WARNING: Failed to fetch URL http://dotat.at/prog/unifdef/unifdef-2.10.tar.xz, 
attempting MIRRORS if available
NOTE: Tasks Summary: Attempted 152 tasks of which 0 didn't need to be rerun and 
2 failed.

"


According to the errors, It seams there are many fetcher failures,but when I 
copy the link such as"http://kernel.org/pub/linux/kernel/v4.x/linux-4.1.tar.xz"; 
 to my firefox explorer, It could find the files. It is very weird.




If you have any idea about it, pls contact with me.
Thanks




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

Re: [yocto] [meta-raspberrypi] errors when I "bitbake" an image for my rpi2 B+ board

2016-02-02 Thread SIVA SUBRAMANIAN.P 
Hi Jack,
How about wget or curl of those urls, are you able to reach it? Also, see
if explorer redirects this to https or other protocol?

Regards,
Sivasubramanian

On Wed, Feb 3, 2016 at 8:11 AM, 张健  wrote:

> [meta-raspberrypi]
> Hi,every one.
> I'm trying to use meta-raspberrypi layer to build an image for my
> raspberrypi2 B+ board.
>
> After I download poky,I git clone meta-raspberrypi layer as follows: "git
> clone git://git.yoctoproject.org/meta-raspberrypi"
> Then I totally follow the README in the meta-raspberrypi directory as
> follows:
> "
> .
> How to use it:
>
> 1. source poky/oe-init-build-env rpi-build
> 2. Add needed layer to bblayers.conf:
> - meta-raspberrypi
> 3  Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf  (I set
> machine to be "raspberrypi2" here)
> 4. bitbake rpi-hwup-image
> 5. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is
> used)
> 6. Boot your RPI.
> "
>
> but it comes out with several errors after "bitbake", I don't know why, 
> warnings
> and errors are as follows:
> "
> WARNING: Failed to fetch URL
> ftp://invisible-island.net/ncurses/current/ncurses-5.9-20150329.tgz,
> attempting MIRRORS if available
> WARNING: Failed to fetch URL
> http://kernel.org/pub/linux/kernel/v4.x/linux-4.1.tar.xz, attempting
> MIRRORS if available
> ERROR: Fetcher failure: Fetch command failed with exit code 4, output:
> wget: unable to resolve host address 'kernel.org'
>
> ERROR: Function failed: Fetcher failure for URL: '
> http://kernel.org/pub/linux/kernel/v4.x/linux-4.1.tar.xz'. Unable to
> fetch URL from any source.
> ERROR: Logfile of failure stored in:
> /home/jackzhang1992/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/linux-libc-headers/4.1-r0/temp/log.do_fetch.8031
> ERROR: Task 961
> (/home/jackzhang1992/poky/meta/recipes-kernel/linux-libc-headers/
> linux-libc-headers_4.1.bb, do_fetch) failed with exit code '1'
> WARNING: Failed to fetch URL
> http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.12.0.0.tar.xz,
> attempting MIRRORS if available
> ERROR: Fetcher failure: Fetch command failed with exit code 4, output:
> wget: unable to resolve host address 'ymorin.is-a-geek.org'
>
> ERROR: Function failed: Fetcher failure for URL: '
> http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.12.0.0.tar.xz'.
> Unable to fetch URL from any source.
> ERROR: Logfile of failure stored in:
> /home/jackzhang1992/poky/build/tmp/work/i686-linux/kconfig-frontends-native/3.12.0.0-r0/temp/log.do_fetch.8067
> ERROR: Task 728
> (virtual:native:/home/jackzhang1992/poky/meta/recipes-devtools/kconfig-frontends/
> kconfig-frontends_3.12.0.0.bb, do_fetch) failed with exit code '1'
> WARNING: Failed to fetch URL
> http://dotat.at/prog/unifdef/unifdef-2.10.tar.xz, attempting MIRRORS if
> available
> NOTE: Tasks Summary: Attempted 152 tasks of which 0 didn't need to be
> rerun and 2 failed.
> "
>
> According to the errors, It seams there are many fetcher failures,but when
> I copy the link such as"
> http://kernel.org/pub/linux/kernel/v4.x/linux-4.1.tar.xz";  to my firefox
> explorer, It could find the files. It is very weird.
>
>
> If you have any idea about it, pls contact with me.
> Thanks
>
>
> Jack
> Shanghai
>
>
> --
> ___
> 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-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set

2016-02-02 Thread Khem Raj 

> On Feb 2, 2016, at 8:50 AM, GUEYTAT Julien  
> wrote:
> 
> Hi,
> 
> It seems that there are some stiff missing between meta-qt5 or 
> meta-raspberrypi.
> When we set the option gles… to qtbase we don’t get the QMAKE_LIBS_EGL set 
> properly.
> We can compare a working set of variables in the qt mkspecs directory of qt.
> There is one dedicated file for the RaspberryPi2. May be one also for 
> RaspberryPi.
> Anyway!
> How could we set those *_EGL variables properly? And… If they are properly 
> set, will qtbase will take them into account?
> 
> I will be happy to propose a patch but I need to get more precision first.

Firstly show the DISTRO_FEATURES may be you are missing some important knobs 
for EGL
like openGL and gles2 etc.

> Thanks in advance,
> 
> 
> 
> Julien GUEYTAT
> Ingénieur Informatique
> 
> 1027, avenue du Docteur Julien Lefebre BP27
> 06271 Villeneuve-Loubet Cedex
> Fixe :  +33 (0) 492 024 545
> Mob :  +33(0) 617 980 383
> Fax :+33(0) 492 024 546
> Email : j.guey...@cdssoft.studiel.fr 
> www : www.studiel.fr 
> P Pensez Environnement, imprimez seulement si nécessaire
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org 
> https://lists.yoctoproject.org/listinfo/yocto 
> 


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

Re: [yocto] [meta-raspberrypi] errors when I "bitbake" an image formy rpi2 B+ board

2016-02-02 Thread 张健 
Hi, Sivasubramanian:
Yes, I am able to reach it by using my firefox browser to reach it, It works. 
And that's the most werid thing.
I'v asked this question on the '#yocto' IRC channel after I sent the first mail.
  Someone in the channel told me to use the command: " bitbake 
kconfig-frontends-native -c fetch" to fetch  . then use "bitbake 
rpi-hwup-image". My computer is building now, and I'm waiting to see the 
results.
  Another possible reason is maybe the speed of the internet.  I used "wifi" 
and the linux is run under the VMware; Now I  connect the cable  to my 
computer(not wireless anymore), still linux in the VMware, though. And try 
"bitbake", and wait for the result.


Thanks,


Jack
Shanghai
 
-- Original --
From:  "SIVA SUBRAMANIAN.P";
Date:  Wed, Feb 3, 2016 02:19 PM
To:  "JackZhang"; 
Cc:  "yocto"; 
Subject:  Re: [yocto] [meta-raspberrypi] errors when I "bitbake" an image formy 
rpi2 B+ board

 
Hi Jack,

How about wget or curl of those urls, are you able to reach it? Also, see if 
explorer redirects this to https or other protocol?


Regards,

Sivasubramanian


On Wed, Feb 3, 2016 at 8:11 AM, 张健  wrote:
[meta-raspberrypi]
Hi,every one. 
I'm trying to use meta-raspberrypi layer to build an image for my raspberrypi2 
B+ board. 


After I download poky,I git clone meta-raspberrypi layer as follows: "git clone 
git://git.yoctoproject.org/meta-raspberrypi"

Then I totally follow the README in the meta-raspberrypi directory as follows:
"
.
How to use it:


1. source poky/oe-init-build-env rpi-build
2. Add needed layer to bblayers.conf:
- meta-raspberrypi
3  Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf  (I set machine to 
be "raspberrypi2" here)
4. bitbake rpi-hwup-image
5. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is used)
6. Boot your RPI.

"


but it comes out with several errors after "bitbake", I don't know why, 
warnings and errors are as follows:
"
WARNING: Failed to fetch URL 
ftp://invisible-island.net/ncurses/current/ncurses-5.9-20150329.tgz, attempting 
MIRRORS if available
WARNING: Failed to fetch URL 
http://kernel.org/pub/linux/kernel/v4.x/linux-4.1.tar.xz, attempting MIRRORS if 
available
ERROR: Fetcher failure: Fetch command failed with exit code 4, output:
wget: unable to resolve host address 'kernel.org'


ERROR: Function failed: Fetcher failure for URL: 
'http://kernel.org/pub/linux/kernel/v4.x/linux-4.1.tar.xz'. Unable to fetch URL 
from any source.
ERROR: Logfile of failure stored in: 
/home/jackzhang1992/poky/build/tmp/work/cortexa7hf-vfp-vfpv4-neon-poky-linux-gnueabi/linux-libc-headers/4.1-r0/temp/log.do_fetch.8031
ERROR: Task 961 
(/home/jackzhang1992/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.1.bb,
 do_fetch) failed with exit code '1'
WARNING: Failed to fetch URL 
http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.12.0.0.tar.xz,
 attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 4, output:
wget: unable to resolve host address 'ymorin.is-a-geek.org'


ERROR: Function failed: Fetcher failure for URL: 
'http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.12.0.0.tar.xz'.
 Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: 
/home/jackzhang1992/poky/build/tmp/work/i686-linux/kconfig-frontends-native/3.12.0.0-r0/temp/log.do_fetch.8067
ERROR: Task 728 
(virtual:native:/home/jackzhang1992/poky/meta/recipes-devtools/kconfig-frontends/kconfig-frontends_3.12.0.0.bb,
 do_fetch) failed with exit code '1'
WARNING: Failed to fetch URL http://dotat.at/prog/unifdef/unifdef-2.10.tar.xz, 
attempting MIRRORS if available
NOTE: Tasks Summary: Attempted 152 tasks of which 0 didn't need to be rerun and 
2 failed.

"


According to the errors, It seams there are many fetcher failures,but when I 
copy the link such as"http://kernel.org/pub/linux/kernel/v4.x/linux-4.1.tar.xz"; 
 to my firefox explorer, It could find the files. It is very weird.




If you have any idea about it, pls contact with me.
Thanks




Jack
Shanghai




--
 ___
 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-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set

2016-02-02 Thread Yannick Kiekens 
Have a look at this git repo: https://github.com/YannickKiekens/meta-qt5-pi

I have build a qt5 eglfs with raspberry pi2 backend on master branch
yesterday evening

On Wed, Feb 3, 2016 at 7:08 AM, Khem Raj  wrote:

>
> On Feb 2, 2016, at 8:50 AM, GUEYTAT Julien 
> wrote:
>
> Hi,
>
> It seems that there are some stiff missing between meta-qt5 or
> meta-raspberrypi.
> When we set the option gles… to qtbase we don’t get the QMAKE_LIBS_EGL set
> properly.
> We can compare a working set of variables in the qt mkspecs directory of
> qt.
> There is one dedicated file for the RaspberryPi2. May be one also for
> RaspberryPi.
> Anyway!
> How could we set those *_EGL variables properly? And… If they are properly
> set, will qtbase will take them into account?
>
> I will be happy to propose a patch but I need to get more precision first.
>
>
> Firstly show the DISTRO_FEATURES may be you are missing some important
> knobs for EGL
> like openGL and gles2 etc.
>
> Thanks in advance,
>
>
>
> *Julien GUEYTAT*
> *Ingénieur Informatique*
> 
> 1027, avenue du Docteur Julien Lefebre BP27
> 06271 Villeneuve-Loubet Cedex
> *Fixe* :  +33 (0) 492 024 545
> *Mob* :  +33(0) 617 980 383
> *Fax* :+33(0) 492 024 546
> *Email* : j.guey...@cdssoft.studiel.fr
> *www* : www.studiel.fr
> *P* *Pensez Environnement, imprimez seulement si nécessaire*
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto