[yocto] cups: 2.1.4 cups-filter build

[Weng Josn]

Hello,

I'm testing cups: 2.1.4 I need to serial backend support. How to compile or
enable serial backend support ?

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

Re: [yocto] [meta-raspberrypi] gles2 on raspi3

[Changhyeok Bae]

FYI

If you are using morty branch, mesa version should be upgraded to v12.0.3
for vc4 bug fix. There is some vc4 patches between v12.0.1 and v12.0.3 of
mesa.

Thanks
Changhyeok

2017-04-17 10:11 GMT+09:00 Andreas Müller :

> On Mon, Apr 17, 2017 at 2:27 AM, Trevor Woerner 
> wrote:
> > On Mon 2017-04-17 @ 01:52:57 AM, Andreas Müller wrote:
> >> On Sun, Apr 16, 2017 at 1:16 AM, Trevor Woerner 
> wrote:
> >> > w00T! \O/
> >> >
> >> > Swapping out meta-raspberrypi for your meta-raspi-light works!!! I
> now have
> >> > accelerated glmark2-es2 ~40FPS :-D
> >> 40fps for glmark-es2 (did you mean glxgears)? The total result I get
> >> for Pi3 on X11 (xfce) is ~105-117 depending on cpu-governor. I don't
> >> know what Desktop/window manager you use but for graphics benchmarking
> >> you should disable compositor.
> >
> > ;-) haha ;-)
> > You couldn't just let me be happy?!
> OK - I am really sorry for this :
> > Yesterday it was running at 1FPS (*one*!! and probably less)
> > ;-) haha ;-)
> >
> > I'm using openbox, I can't imagine anything more minimal than that. But I
> > think I see where the difference lies. I usually run glmark2-es2
> fullscreen.
> Yeah openbox seems light weight and does no compositing.
> > When I run it in its own little window:
> >
> > root@raspberrypi3:~# glmark2-es2
> > MESA-LOADER: device is not located on the PCI bus
> > MESA-LOADER: device is not located on the PCI bus
> > MESA-LOADER: device is not located on the PCI bus
> > ===
> > glmark2 2014.03
> > ===
> > OpenGL Information
> > GL_VENDOR: Broadcom
> > GL_RENDERER:   Gallium 0.4 on VC4 V3D 2.1
> > GL_VERSION:OpenGL ES 2.0 Mesa 17.0.2
> > ===
> > [build] use-vbo=false: FPS: 126 FrameTime: 7.937 ms
> > [build] use-vbo=true: FPS: 140 FrameTime: 7.143 ms
> > [texture] texture-filter=nearest: FPS: 146 FrameTime: 6.849 ms
> > [texture] texture-filter=linear: FPS: 141 FrameTime: 7.092 ms
> > [texture] texture-filter=mipmap: FPS: 135 FrameTime: 7.407 ms
> > [shading] shading=gouraud: FPS: 118 FrameTime: 8.475 ms
> > [shading] shading=blinn-phong-inf: FPS: 102 FrameTime: 9.804 ms
> > [shading] shading=phong: FPS: 69 FrameTime: 14.493 ms
> > [shading] shading=cel: FPS: 69 FrameTime: 14.493 ms
> > [bump] bump-render=high-poly: FPS: 68 FrameTime: 14.706 ms
> > [bump] bump-render=normals: FPS: 154 FrameTime: 6.494 ms
> > [bump] bump-render=height: FPS: 148 FrameTime: 6.757 ms
> > [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 106 FrameTime: 9.434
> ms
> > [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 71
> FrameTime: 14.085 ms
> > [pulsar] light=false:quads=5:texture=false: FPS: 129 FrameTime:
> 7.752 ms
> > [desktop] 
> > blur-radius=5:effect=blur:passes=1:separable=true:windows=4:
> FPS: 44 FrameTime: 22.727 ms
> > [desktop] effect=shadow:windows=4: FPS: 90 FrameTime: 11.111 ms
> > [buffer] columns=200:interleave=false:
> update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 63
> FrameTime: 15.873 ms
> > [buffer] columns=200:interleave=false:
> update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 62
> FrameTime: 16.129 ms
> > [buffer] columns=200:interleave=true:
> update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 73
> FrameTime: 13.699 ms
> > [ideas] speed=duration: FPS: 132 FrameTime: 7.576 ms
> > [jellyfish] : FPS: 98 FrameTime: 10.204 ms
> > [terrain] : FPS: 5 FrameTime: 200.000 ms
> > [shadow] : FPS: 79 FrameTime: 12.658 ms
> > [refract] : FPS: 20 FrameTime: 50.000 ms
> > [conditionals] fragment-steps=0:vertex-steps=0: FPS: 145
> FrameTime: 6.897 ms
> > [conditionals] fragment-steps=5:vertex-steps=0: FPS: 124
> FrameTime: 8.065 ms
> > [conditionals] fragment-steps=0:vertex-steps=5: FPS: 145
> FrameTime: 6.897 ms
> > [function] fragment-complexity=low:fragment-steps=5: FPS: 139
> FrameTime: 7.194 ms
> > [function] fragment-complexity=medium:fragment-steps=5: FPS: 39
> FrameTime: 25.641 ms
> > [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5:
> FPS: 135 FrameTime: 7.407 ms
> > [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5:
> FPS: 136 FrameTime: 7.353 ms
> > [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5:
> FPS: 91 FrameTime: 10.989 ms
> > ===
> >   glmark2 Score: 101
> > ===
> > 

Re: [yocto] Noobie questions

[Gary Thomas]

On 2017-04-17 16:27, bahjat khan wrote:

Hi Gary,


n.b. it's polite to keep responses on the mailing list so that everyone 
benefits!




Thanks for the response!


How will i know what to change in the local.conf file?
Is there a Yocto article that tells me what the different variables in .bb and 
.conf files mean?


The Yocto (OpenEmbedded) documentation is quite thorough.
  https://www.yoctoproject.org/documentation



*From:* yocto-boun...@yoctoproject.org  on behalf of 
Gary Thomas 
*Sent:* 17 April 2017 12:59
*To:* yocto@yoctoproject.org
*Subject:* Re: [yocto] Noobie questions

On 2017-04-16 20:23, bahjat khan wrote:

Hi Guys,


I'm extremely new to the yocto project, i've done quite a bit of reading on it 
but i'm still very confused.

I've set my self a simple task of changing the kernel for a Yocto image that i 
build, the commands i use to build this
yocto image are:



  $ git clone http://git.yoctoproject.org/git/poky
  $ cd poky
  $ git checkout -b fido origin/fido
  $ source oe-init-build-env
  $bitbake core-image-minimal
  $runqemu qemux86

Check out a newer revision - fido is VERY OLD.  Probably best to use morty 
which is the upcoming 2.3 release



|$ git clone http://git.yoctoproject.org/git/poky $ cd poky $ git checkout -b 
fido origin/fido $ source oe-init-build-env
$bitbake core-image-minimal $runqemu qemux86|

I understand that i need to make changes to the poky.conf file to specify what 
kernel i want to use (i have a standard
choice between 3.14 and 3.19).


No, make such changes in your local.conf



However if i want to use a different kernel such as 4.4, i do this by making 
the changes in the poky.conf file, copying
linux-yocto_3.19.bb file and renaming it to linux-yocto_4.4.bb. I also change 
the SRC_URI to
"git://git.yoctoproject.org/linux-yocto-4.4.git;barcelone=1;branch=${KRBRANCH},${KMETA};name=machine,meta"

It doesn't seem to find the place where it needs to download 4.4 from even 
though it's on the yocto website. I can
download it by simply typing "git clone "

Also i haven't changed the SRCREV_machine_qemuarm ?= "" numbers, 
because i don't know what they are or what
the variable SRCREV_machine_qemuarm is.


You should never need to mess with these settings.



With these warnings, it reverts back to 3.19 kernel.

I hope i've explained my problem well, but if you are still confused please let 
me know.




--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

[linux-yocto] [PATCH] base.cfg: Add POSIX_TIMERS to fix ping hang

[Saul Wold]

busybox ping was hanging after 1 loop with 4.10.x/4.11.x kernel.
ping was hanging waiting for alarm to expire.
4.10.x kernel intrdoduced new kernel config CONFIG_POSIX_TIMERS
which needs to be enabled to enable calls timer_create, settimer,
alarm etc.

Signed-off-by: Kushwaha, Priyalee 
Signed-off-by: Saul Wold 
---
Targeted for 4.10 and beyond

 ktypes/base/base.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/ktypes/base/base.cfg b/ktypes/base/base.cfg
index 91a140b..062f6e3 100644
--- a/ktypes/base/base.cfg
+++ b/ktypes/base/base.cfg
@@ -23,6 +23,7 @@ CONFIG_LOCALVERSION=""
 CONFIG_SWAP=y
 CONFIG_SYSVIPC=y
 CONFIG_POSIX_MQUEUE=y
+CONFIG_POSIX_TIMERS=y
 CONFIG_BSD_PROCESS_ACCT=y
 CONFIG_BSD_PROCESS_ACCT_V3=y
 # CONFIG_AUDIT is not set
-- 
2.7.4

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

Re: [yocto] meta-tensorflow

[Khem Raj]

On Mon, Apr 17, 2017 at 2:19 PM, Giuseppe Di Guglielmo
 wrote:
> Hi,
> is there any of the meta- layers supporting the installation of Google
> TensorFlow? Does a package-specific layer make sense in Yocto?
>

Don't think so. There is tensor rt recipe in tegra bsp layer

https://github.com/madisongh/meta-tegra/tree/master/recipes-devtools/gie

but it would be interesting to have a tensor flow layer if its going
to involve multiple packages.

> GDG
>
> --
> ___
> 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-tensorflow

[Giuseppe Di Guglielmo]

Hi,
is there any of the meta- layers supporting the installation of Google
TensorFlow? Does a package-specific layer make sense in Yocto?

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

[yocto] [patchwork][PATCH v2] models.py: Improve Series naming when no cover letter is provided

[Jose Lamego]

The number/order prefix from a patch Subject line
is inapropriately included when naming a Series where
a cover letter is not provided and an additional
prefix is present at the Subject.

This change improves the substitution regex to omit
the number/order and any other prefix that may be
present.

[YOCTO #11305]

Signed-off-by: Jose Lamego 
---

Notes:
Changes in v2: Ommit all of the prefixes that may be present in first patch 
to name the series

 patchwork/models.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/patchwork/models.py b/patchwork/models.py
index ddc3254..a34e0fc 100644
--- a/patchwork/models.py
+++ b/patchwork/models.py
@@ -1046,7 +1046,7 @@ def _on_revision_complete(sender, revision, **kwargs):
 # so we can update the name for series without a cover letter
 if series.name == SERIES_DEFAULT_NAME:
 name = series.latest_revision().ordered_patches()[0].name
-n = re.compile(r'(\[\d+\/\d+\]\s?)')
+n = re.compile(r'(\[.*\]\s?)')
 name = n.sub('', name)
 c = len(series.latest_revision().ordered_patches())
 # For one-patch series (1/1) without cover letter
-- 
2.7.4

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

Re: [yocto] Fwd: iMX6UL - QtQuick - QtQuick2DRenderer

[Andreas Cord-Landwehr]

Hi, one point I noticed directly, you should only use one "-", i.e. 
"-platform linuxfb" . Moreover, best check with "export QT_DEBUG_PLUGINS=1" 
that linuxfb is located and loaded correctly.
Only if all of this works fine, you should start looking into the compile 
options.

Cheers,
Andreas

On Thursday, April 6, 2017 10:35:20 AM CEST Stefano Zuín wrote:
>  Mensaje reenviado 
> Asunto:   [yocto] iMX6UL - QtQuick - QtQuick2DRenderer
> Fecha:Wed, 5 Apr 2017 13:29:13 +0200
> De:   Stefano Zuín 
> Para: yocto@yoctoproject.org
> 
> 
> 
> Hi all,
> 
> I'm trying to run a graphical Qt application based in QtQuick2 and QML
> (example calqtr) in my iMX6UL (Variscite's Dart6UL). As this device
> doesn't have GPU, I have to use QtQuick2DRenderer to substitute openGL.
> I'm using Ubuntu 14.04 64bits and Krogoth 2.1.2
> 
> I have the enterprise license, followed the Qt's instructions
> (http://doc.qt.io/QtQuick2DRenderer/qtquick2drenderer-installation-guide.htm
> l) and use the qmake built with meta-toolchain-qt5. So QtQuick2DRenderer is
> correctly installed.
> 
> Then, before run the app, I declared export
> QMLSCENE_DEVICE=softwarecontext before running the application.
> Unfortunately, I get the next message when try to run a demo example:
> 
> ./calqlatr --platform linuxfb
> QML debugging is enabled. Only use this in a safe environment.
> This plugin does not support createPlatformOpenGLContext!
> Failed to create OpenGL context for format QSurfaceFormat(version 2.0,
> options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize
> -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples
> -1, swapBehavior 2, swapInterval 1, profile  0)
> Aborted (core dumped)
> 
> I did the SDK using meta-toolchain-qt5 and the image with fsl-image-qt5.
> When I run a console app or a graphical which uses QtQuick 1, it works
> correctly.
> 
> This is my conf/local.conf file:
> 
> MACHINE ??= 'imx6ul-var-dart'
> DISTRO ?= 'fsl-imx-fb'
> PACKAGE_CLASSES ?= "package_rpm"
> EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
> USER_CLASSES ?= "buildstats image-mklibs"
> PATCHRESOLVE = "noop"
> BB_DISKMON_DIRS = "\
>   STOPTASKS,${TMPDIR},1G,100K \
>   STOPTASKS,${DL_DIR},1G,100K \
>   STOPTASKS,${SSTATE_DIR},1G,100K \
>   STOPTASKS,/tmp,100M,100K \
>   ABORT,${TMPDIR},100M,1K \
>   ABORT,${DL_DIR},100M,1K \
>   ABORT,${SSTATE_DIR},100M,1K \
>   ABORT,/tmp,10M,1K"
> PACKAGECONFIG_append_pn-qemu-native = " sdl"
> PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
> CONF_VERSION = "1"
> 
> DL_DIR ?= "${BSPDIR}/downloads/"
> ACCEPT_FSL_EULA = "1"
> 
> # Add Eclipse debug and Qt creator support to your images
> EXTRA_IMAGE_FEATURES = " \
>   debug-tweaks \
>   tools-debug \
>   eclipse-debug \
> "
> 
> IMAGE_INSTALL_append = " \
>   tcf-agent \
>   openssh-sftp-server \
>  qtbase-fonts \
>   qtbase-plugins \
>   qtbase-tools \
>   qtbase-examples \
>   qtdeclarative \
>   qtdeclarative-plugins \
>   qtdeclarative-tools \
>   qtdeclarative-examples \
>   qtdeclarative-qmlplugins \
>   qtquickcontrols-qmlplugins \
> "
> 
> # Use systemd instead of SysV init
> DISTRO_FEATURES_append = " systemd"
> VIRTUAL-RUNTIME_init_manager = "systemd"
> DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
> VIRTUAL-RUNTIME_initscripts = ""
> IMX_DEFAULT_DISTRO_FEATURES_append = " systemd"
> 
> 
> I think, that problem could be in configuring -opengl es2 in qtbase
> recipe. But when I set it manually I get errors doing bitbake
> fsl-image-qt5
> 
> 
> 
> Este correo electrónico y sus documentos adjuntos contienen información
> privilegiada, personal y estrictamente confidencial, y está prohibida la
> copia, reenvío o utilización de la información. Si usted no es la persona
> destinataria del presente mensaje, no está autorizada a leerlo, retenerlo o
> difundirlo.
> 
> This e-mail and its attachments are privileged, confidential and contain
> private information, and any sending, using or copy of its information is
> prohibited. Any person other than its intended recipient is not authorised
> to read, retain or distribute this information.


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

Re: [yocto] Bug 11307 - sstate.bbclass tries to modify mirror files

[Christopher Larson]

On Tue, Apr 11, 2017 at 11:37 PM, Paulo Neves  wrote:

> Commit 51edde653707e7a3cd2186082458f01f32cd1996 makes a wrong
> assumption that SSTATE_MIRRORS have write permissions.
>
> A mirror is by definition outside of it's user control. In my use case
> it happens I does not have permissions to update the access time of
> the dereferenced symbolic-link file.
>
> If we had the possibility to modify the sstate-mirror we would have
> set SSTATE_DIR instead. There are 3 possible fixes:
>
> * Revert this patch. It seems tailored to a very special use case
> which breaks the definition of mirror.
> * Only touch the file if the file access time is writeable.
> * Set (yet) another option to touch SSTATE_MIRROR files.
>
> I also can imagine this raising sever performance issues if the mirror
> is used by several users at the same time. The server will need to
> update the file meta data every time
>
> This patch fixes the bug with minimal impact on the original
> functionality. Option 2
>
>
> Related to (https://bugzilla.yoctoproject.org/show_bug.cgi?id=10857)
>
> From aa8cab9660744c8d5277f8e82f10a844884aff78 Mon Sep 17 00:00:00 2001
> From: Paulo Neves 
> Date: Tue, 11 Apr 2017 10:57:47 +0300
> Subject: [PATCH] Added test for write ability of sstate-mirror .siginfo
>

Thanks much for your contribution, this seems reasonable to me. That said,
the subject line needs tweaking to meet our commit message guidelines,
i.e.: sstate.bbclass: handle non-writable sstate mirror, or similar. And
the yocto bug id should go in the body, not the subject line. I realize it
probably sounds nitpicky, but maintaining commit message quality makes it
much easier to review the logs in the future. This file is also in the
oe-core layer, so the patch should ideally go to the openembedded-core
mailing list. Thanks again!

See http://openembedded.org/wiki/Commit_Patch_Message_Guidelines.
-- 
Christopher Larson
kergoth at gmail dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Senior Software Engineer, Mentor Graphics
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Static Lib build.

[Weng Josn]

Hi

Yes I can provide and logs. What type logs do you need ?

Thanks.

2017-04-17 7:40 GMT+01:00 Fabien Lahoudere :
> On Sat, 2017-04-15 at 17:24 +0300, Life Life wrote:
>> Hello,
>>
>> I'm try to build static library for SDK.
>>
>> Update the build/local.conf file with the following information
>>
>> SDKIMAGE_FEATURES = "staticdev-pkgs dev-pkgs"
>>
>> INHERIT += "buildhistory"
>> BUILDHISTORY_COMMIT = "0"
>>  BUILDHISTORY_FEATURES = "sdk"
>>
>> But cannot create static library for SDK.
>
> Can you provide command and logs?
>
>>
>>
>> Thanks.
> --
> ___
> 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-raspberrypi][morty][PATCH 7/7] README: Add info about raspberrypi0-wifi

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 README | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README b/README
index 65a1e5f..17f8273 100644
--- a/README
+++ b/README
@@ -77,6 +77,7 @@ b. Add needed layer to bblayers.conf:
 c. Set MACHINE in local.conf to one of the supported boards:
 - raspberrypi
 - raspberrypi0
+- raspberrypi0-wifi
 - raspberrypi2
 - raspberrypi3
 - raspberrypi-cm (dummy alias for raspberrypi)
@@ -243,11 +244,10 @@ List of currently supported models:
 
 3.O. Enable UART
 ===
+RaspberryPi 0, 1, 2 and CM will have UART console enabled by default.
 
-RaspberryPi 1, 2 and CM will have UART console enabled by default.
-
-RaspberryPi 3 does not have the UART enabled by default because this needs a
-fixed core frequency and enable_uart wil set it to the minimum. Certain
+RaspberryPi 0 WiFi and 3 does not have the UART enabled by default because this
+needs a fixed core frequency and enable_uart wil set it to the minimum. Certain
 operations - 60fps h264 decode, high quality deinterlace - which aren't
 performed on the ARM may be affected, and we wouldn't want to do that to users
 who don't want to use the serial port. Users who want serial console support on
-- 
2.12.2

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

[yocto] [meta-raspberrypi][morty][PATCH 4/7] firmware.inc: Bump to 20170405

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 recipes-bsp/common/firmware.inc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
index 53c469e..1c3a911 100644
--- a/recipes-bsp/common/firmware.inc
+++ b/recipes-bsp/common/firmware.inc
@@ -1,10 +1,10 @@
-RPIFW_DATE ?= "20170303"
+RPIFW_DATE ?= "20170405"
 RPIFW_SRC_URI ?= 
"https://github.com/raspberrypi/firmware/archive/1.${RPIFW_DATE}.tar.gz;
 RPIFW_S ?= "${WORKDIR}/firmware-1.${RPIFW_DATE}"
 
 SRC_URI = "${RPIFW_SRC_URI}"
-SRC_URI[md5sum] = "c87bc1bffbb8f254fc739e34baa03b02"
-SRC_URI[sha256sum] = 
"ee8758d7e63c8fea7c8b7b476ff1c09f9591c74349b7751036a78ae5b88eca36"
+SRC_URI[md5sum] = "ea82d14a7cd8cfae9b78e00d4e56bc71"
+SRC_URI[sha256sum] = 
"2f4e5bddbac1372590db203002c35cbba3fb9d6172a93c314ee27bf05ae13bff"
 
 PV = "${RPIFW_DATE}"
 
-- 
2.12.2

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

[yocto] [meta-raspberrypi][morty][PATCH 1/7] linux-firmware: Bring up wifi/ble interface on rpi3

[Andrei Gherzan]

From: Khem Raj 

Currently the firmware is installed but kernel fails to load it
due this .txt file missing in the firmware directory and it ends
up with wifi/bluetooth i/f not being initialized. The error is
also in dmesg

[3.120991] usbcore: registered new interface driver brcmfmac
[3.148240] brcmfmac mmc1:0001:1: Direct firmware load for 
brcm/brcmfmac43430-sdio.txt failed with error -2

After applying this patch now ifconfig -a can list wlan0 interface
successfully.

Signed-off-by: Khem Raj 
Signed-off-by: Andrei Gherzan 
---
 .../linux-firmware/files/brcmfmac43430-sdio.txt| 66 ++
 .../linux-firmware/linux-firmware_%.bbappend   | 12 
 2 files changed, 78 insertions(+)
 create mode 100644 recipes-kernel/linux-firmware/files/brcmfmac43430-sdio.txt
 create mode 100644 recipes-kernel/linux-firmware/linux-firmware_%.bbappend

diff --git a/recipes-kernel/linux-firmware/files/brcmfmac43430-sdio.txt 
b/recipes-kernel/linux-firmware/files/brcmfmac43430-sdio.txt
new file mode 100644
index 000..ea4f648
--- /dev/null
+++ b/recipes-kernel/linux-firmware/files/brcmfmac43430-sdio.txt
@@ -0,0 +1,66 @@
+# NVRAM file for BCM943430WLPTH
+# 2.4 GHz, 20 MHz BW mode
+
+# The following parameter values are just placeholders, need to be updated.
+manfid=0x2d0
+prodid=0x0727
+vendid=0x14e4
+devid=0x43e2
+boardtype=0x0727
+boardrev=0x1101
+boardnum=22
+macaddr=00:90:4c:c5:12:38
+sromrev=11
+boardflags=0x00404201
+boardflags3=0x0800
+xtalfreq=37400
+nocrc=1
+ag0=255
+aa2g=1
+ccode=ALL
+
+pa0itssit=0x20
+extpagain2g=0
+#PA parameters for 2.4GHz, measured at CHIP OUTPUT
+pa2ga0=-168,7161,-820
+AvVmid_c0=0x0,0xc8
+cckpwroffset0=5
+
+# PPR params
+maxp2ga0=84
+txpwrbckof=6
+cckbw202gpo=0
+legofdmbw202gpo=0x6611
+mcsbw202gpo=0x7771
+propbw202gpo=0xdd
+
+# OFDM IIR :
+ofdmdigfilttype=18
+ofdmdigfilttypebe=18
+# PAPD mode:
+papdmode=1
+papdvalidtest=1
+pacalidx2g=42
+papdepsoffset=-22
+papdendidx=58
+
+# LTECX flags
+ltecxmux=0
+ltecxpadnum=0x0102
+ltecxfnsel=0x44
+ltecxgcigpio=0x01
+
+il0macaddr=00:90:4c:c5:12:38
+wl0id=0x431b
+
+deadman_to=0x
+# muxenab: 0x1 for UART enable, 0x2 for GPIOs, 0x8 for JTAG
+muxenab=0x1
+# CLDO PWM voltage settings - 0x4 - 1.1 volt
+#cldo_pwm=0x4
+
+#VCO freq 326.4MHz
+spurconfig=0x3 
+
+edonthd20l=-75
+edoffthd20ul=-80
diff --git a/recipes-kernel/linux-firmware/linux-firmware_%.bbappend 
b/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
new file mode 100644
index 000..252da22
--- /dev/null
+++ b/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
@@ -0,0 +1,12 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
+
+SRC_URI += "file://brcmfmac43430-sdio.txt"
+
+do_install_append() {
+   install -D -m 0644 ${WORKDIR}/brcmfmac43430-sdio.txt 
${D}/lib/firmware/brcm/brcmfmac43430-sdio.txt
+}
+
+FILES_${PN}-bcm43430 += " \
+  /lib/firmware/brcm/brcmfmac43430-sdio.txt \
+"
+
-- 
2.12.2

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

[yocto] [meta-raspberrypi][morty][PATCH 6/7] raspberrypi0-wifi.conf: Add machine configuration file

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 conf/machine/raspberrypi0-wifi.conf | 11 +++
 1 file changed, 11 insertions(+)
 create mode 100644 conf/machine/raspberrypi0-wifi.conf

diff --git a/conf/machine/raspberrypi0-wifi.conf 
b/conf/machine/raspberrypi0-wifi.conf
new file mode 100644
index 000..2b7cea4
--- /dev/null
+++ b/conf/machine/raspberrypi0-wifi.conf
@@ -0,0 +1,11 @@
+#@TYPE: Machine
+#@NAME: RaspberryPi Zero WiFi Development Board
+#@DESCRIPTION: Machine configuration for the RaspberryPi Zero  WiFi board 
(https://www.raspberrypi.org/blog/raspberry-pi-zero-w-joins-family/)
+
+MACHINEOVERRIDES = "raspberrypi:${MACHINE}"
+include conf/machine/raspberrypi.conf
+
+MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
+
+SERIAL_CONSOLE = "115200 ttyS0"
+VC4_CMA_SIZE ?= "cma-128"
-- 
2.12.2

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

[yocto] [meta-raspberrypi][morty][PATCH 5/7] rpi-base.inc: Include dtb for RPI0 WiFi

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 conf/machine/include/rpi-base.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index e069e70..dc98099 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -14,6 +14,7 @@ XSERVER = " \
 "
 
 KERNEL_DEVICETREE ?= " \
+bcm2708-rpi-0-w.dtb \
 bcm2708-rpi-b.dtb \
 bcm2708-rpi-b-plus.dtb \
 bcm2709-rpi-2-b.dtb \
-- 
2.12.2

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

[yocto] Noobie questions

[bahjat khan]

Hi Guys,


I'm extremely new to the yocto project, i've done quite a bit of reading on it 
but i'm still very confused.

I've set my self a simple task of changing the kernel for a Yocto image that i 
build, the commands i use to build this yocto image are:


 $ git clone http://git.yoctoproject.org/git/poky
 $ cd poky
 $ git checkout -b fido origin/fido
 $ source oe-init-build-env
 $bitbake core-image-minimal
 $runqemu qemux86

I understand that i need to make changes to the poky.conf file to specify what 
kernel i want to use (i have a standard choice between 3.14 and 3.19).


However if i want to use a different kernel such as 4.4, i do this by making 
the changes in the poky.conf file, copying linux-yocto_3.19.bb file and 
renaming it to linux-yocto_4.4.bb. I also change the SRC_URI to 
"git://git.yoctoproject.org/linux-yocto-4.4.git;barcelone=1;branch=${KRBRANCH},${KMETA};name=machine,meta"

It doesn't seem to find the place where it needs to download 4.4 from even 
though it's on the yocto website. I can download it by simply typing "git clone 
"

Also i haven't changed the SRCREV_machine_qemuarm ?= "" numbers, 
because i don't know what they are or what the variable SRCREV_machine_qemuarm 
is.

With these warnings, it reverts back to 3.19 kernel.

I hope i've explained my problem well, but if you are still confused please let 
me know.

Kind Regards,

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

[yocto] How to write a recipe to add files/links in yocto rootfs

[Jaggi, Manish]

Hi

When I run bitbake core-image-minimal  a rootfs is generated.
I have to create links to some files in the rootfs, and add some files.
How to create a recipe which does that ?

I thought of trying to extend do_rootfs but that didnt work.

 Regards, 
Manish Jaggi
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Symbolic link to ld-linux-armhf.so.3

[Fabien Lahoudere]

On Sat, 2017-04-15 at 20:47 +0200, Alvaro Garcia wrote:
> Hi, I made a recipe for hamachi. Hamachi looks for /lib/ld-linux.so.3 but in 
> my poky build this
> file is /lib/ld-linux-armhf.so.3.
> 
> If I do ln -s /lib/ld-linux-armhf.so.3 /lib/ld-linux.so.3 hamachi runs fine 
> so the solution its
> just a symbolic link. My problem is that I cant make this link from my recipe.
> 
> Into my do_install I do: ln -s /lib/ld-linux-armhf.so.3 ${D}/lib/ld-linux.so.3
> But later it does not exist in the rootfs. But if I do:
> ln -sf/lib/ld-linux-armhf.so.3 ${D}/lib/MYPRETTYLIB
> then the link "MYPRETTYLIB" is there. Its like "ld-linux.so.3" is forbidden 
> for some reason.
> 
> I read that some guy had this problem and solved it by using a glibc bbappend 
> but it didnt work
> for me.
> 
> Do I need to do something special to get the "ld-linux.so.3" link?
> 

As Khem Raj said in a previous discussion:
"
that may not be enough. .so are treated as symlinks and shoved into
-dev packages by default. if you need unversioned libraries then you
have to let the system know that its not a dev library symlink

FILES_${PN} += "${libdir}/*.so"
FILES_SOLIBSDEV = ""
INSANE_SKIP_${PN} += "dev-so"
"

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

Re: [yocto] Static Lib build.

[Fabien Lahoudere]

On Sat, 2017-04-15 at 17:24 +0300, Life Life wrote:
> Hello,
> 
> I'm try to build static library for SDK.
> 
> Update the build/local.conf file with the following information
> 
> SDKIMAGE_FEATURES = "staticdev-pkgs dev-pkgs"
> 
> INHERIT += "buildhistory"
> BUILDHISTORY_COMMIT = "0"
>  BUILDHISTORY_FEATURES = "sdk"
> 
> But cannot create static library for SDK.

Can you provide command and logs?

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