Re: [yocto] [oe] [meta-qt5] EGL Error : Could not create the egl surface: error = 0x300b

[Khem Raj]

> On Apr 22, 2016, at 6:07 PM, Ryan Elkholy, PhD, PE  
> wrote:
> 
> Hello,
> 
> I am am trying to make a build that includes meta-qt5 without x11 or
> wayland on the Minnowboard Turbot (x86-64). I was successful in building my
> image but the problem occurred when testing my basic qt app on the image.
> When trying to run the app I get the following error:
> 
> EGL Error : Could not create the egl surface: error = 0x300


Do you have ‘directfb’ in DISTRO_FEATURES
> 
> I have been trying to find a solution for this for weeks with no luck. I am
> able tu run my application when including x11, but I am trying to avoid it.
> Does anyone know any solution for this? Any insight will be helpful because
> I have been stumped for weeks. If nobody knows of a solution is it possible
> to dig deeper into this error and see what is causing it? If so, how?
> 
> Thanks
> --
> ___
> Openembedded-devel mailing list
> openembedded-de...@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel



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

[yocto] [meta-qt5] EGL Error : Could not create the egl surface: error = 0x300b

[Ryan Elkholy, PhD, PE]

Hello,

I am am trying to make a build that includes meta-qt5 without x11 or
wayland on the Minnowboard Turbot (x86-64). I was successful in building my
image but the problem occurred when testing my basic qt app on the image.
When trying to run the app I get the following error:

EGL Error : Could not create the egl surface: error = 0x300

I have been trying to find a solution for this for weeks with no luck. I am
able tu run my application when including x11, but I am trying to avoid it.
Does anyone know any solution for this? Any insight will be helpful because
I have been stumped for weeks. If nobody knows of a solution is it possible
to dig deeper into this error and see what is causing it? If so, how?

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

Re: [yocto] [OE-core] Yocto Project Status WW17

[Burton, Ross]

On 22 April 2016 at 18:04, Trevor Woerner  wrote:
>
> Have the eSDK and CROPS projects been announced publicly? Are they
available
> for us to "play with"?


eSDK is the "extensible SDK', or what appears when you do bitbake image -c
populate_sdk_ext.  This should be in the manual already, the tl;dr is that
its an SDK you can manipulate after installation.

CROPS is docker magic to do builds on Windows/Mac.  Todor did a
presentation at ELC: http:
//events.linuxfoundation.org/sites/events/files/slides/Todor_Minchev_CROPS_ELC_2016.pdf


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

Re: [yocto] [OE-core] Yocto Project Status WW17

[Trevor Woerner]

On Fri 2016-04-22 @ 03:13:21 PM, Jolley, Stephen K wrote:
> o   Encourage adoption of new tools (toaster, eSDK, CROPS)

Have the eSDK and CROPS projects been announced publicly? Are they available
for us to "play with"?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW17

[Jolley, Stephen K]

Current Dev Position: YP 2.1 M4 (Stabilization only milestone.)

Next Deadline: YP 2.1 Final Release Target: April 29, 2016


SWAT team rotation: Ross -> Randy

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

*YP 2.1 M4.rc2 is in QA and it is hoped this will become the final 2.1 
release.

*We have found a number of issues since but nothing with enough impact 
to mean we'd rebuild as yet.

*WDD did continue to fall slightly yet again which is a nice change!

*2.2 planning continues. Current high level plans include:

o   Finishing the integration work of patchwork, patchtest, SWAT team, error 
reporting system and related process improvements

o   "multi-configuration" builds, potentially leading to distributed builds,

o   Moving to python 3.x, at least for Bitbake

o   Encourage adoption of new tools (toaster, eSDK, CROPS)

*If you have enhancements you'd like to see in 2.2, please do make sure 
the bugzilla has entries for them.

*We need to choose a maintainer for 2.1 (krogoth), if interested please 
talk to Richard although we do have some volunteers already.



Key YP 2.1 Dates:

YP 2.1 Final Release Target: April 29, 2016 (Still on Track)


Tracking Metrics:

WDD 2394 (last week 2499)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

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

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

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

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

[If anyone has suggestions for other information you'd like to see on this 
weekly status update, let us know!]

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

[yocto] [meta-raspberrypi][PATCH 5/5] linux-raspberrypi_4.1: Update to v4.1.21

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 recipes-kernel/linux/linux-raspberrypi_4.1.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.1.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
index b55c9ff..79fac66 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
@@ -1,8 +1,8 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.1.18"
+LINUX_VERSION ?= "4.1.21"
 
-SRCREV = "fcc9ad149fbe78e9931b8e769ac54d5430587465"
+SRCREV = "ff45bc0e8917c77461b2901e2743e6339bb70413"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y \
file://0001-dts-add-overlay-for-pitft22.patch \
   "
-- 
2.8.0

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

[yocto] [meta-raspberrypi][PATCH 4/5] bluez5: Add bluez5 support for brcm43438 on raspberrypi3.

[Andrei Gherzan]

From: toolmmy 

This patch adds the bluetooth support for the brcm43438 module on the 
raspberrypi3 by
deploying the modules firmware and changing the targeting firmware path. In 
addition
the brcm43438.service adds the automatically attaching (hciattach) for systemd 
environments.
The following steps can be used to manually configure the brcm43438:

root@raspberrypi3:~# hciattach /dev/ttyAMA0 bcm43xx-3wire
bcm43xx_init
Flash firmware /lib/firmware/brcm/BCM43430A1.hcd
Set Controller UART speed to 300 bit/s
Device setup complete
root@raspberrypi3:~# hciconfig
hci0:   Type: BR/EDR  Bus: UART
BD Address: B8:27:EB:6C:85:BE  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN
RX bytes:983 acl:0 sco:0 events:33 errors:0
TX bytes:887 acl:0 sco:0 commands:33 errors:0

root@raspberrypi3:~# /usr/lib/bluez5/bluetooth/bluetoothd -e -n -E
root@raspberrypi3:~# bluetoothctl
[NEW] Controller B8:27:EB:6C:85:BE raspberrypi3 [default]
[bluetooth]# power on
[CHG] Controller B8:27:EB:6C:85:BE Class: 0x40
Changing power on succeeded
[CHG] Controller B8:27:EB:6C:85:BE Powered: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller B8:27:EB:6C:85:BE Discovering: yes
[NEW] Device 00:1C:05:FF:F9:F8 Nonin3230_501585326

NOTE: SERIAL_CONSOLE must configured to ttyS0 instead of ttyAMA0 (used by the 
brcm43438). See pending patch from Martin Bergek

Signed-off-by: Tom Doehring 
Signed-off-by: Andrei Gherzan 
---
 .../0001-bcm43xx-Add-bcm43xx-3wire-variant.patch   |  26 +++
 ...-UART-speed-must-be-reset-after-the-firmw.patch |  37 +
 ...003-Increase-firmware-load-timeout-to-30s.patch |  25 ++
 ...-Move-the-43xx-firmware-into-lib-firmware.patch |  25 ++
 recipes-connectivity/bluez5/bluez5/BCM43430A1.hcd  | Bin 0 -> 35976 bytes
 .../bluez5/bluez5/brcm43438.service|  12 +++
 recipes-connectivity/bluez5/bluez5_%.bbappend  |  26 +++
 7 files changed, 151 insertions(+)
 create mode 100644 
recipes-connectivity/bluez5/bluez5/0001-bcm43xx-Add-bcm43xx-3wire-variant.patch
 create mode 100644 
recipes-connectivity/bluez5/bluez5/0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
 create mode 100644 
recipes-connectivity/bluez5/bluez5/0003-Increase-firmware-load-timeout-to-30s.patch
 create mode 100644 
recipes-connectivity/bluez5/bluez5/0004-Move-the-43xx-firmware-into-lib-firmware.patch
 create mode 100644 recipes-connectivity/bluez5/bluez5/BCM43430A1.hcd
 create mode 100644 recipes-connectivity/bluez5/bluez5/brcm43438.service
 create mode 100644 recipes-connectivity/bluez5/bluez5_%.bbappend

diff --git 
a/recipes-connectivity/bluez5/bluez5/0001-bcm43xx-Add-bcm43xx-3wire-variant.patch
 
b/recipes-connectivity/bluez5/bluez5/0001-bcm43xx-Add-bcm43xx-3wire-variant.patch
new file mode 100644
index 000..3bc02c4
--- /dev/null
+++ 
b/recipes-connectivity/bluez5/bluez5/0001-bcm43xx-Add-bcm43xx-3wire-variant.patch
@@ -0,0 +1,26 @@
+From b4f2b77472aeb967d3a7595e8a965785c7a37c87 Mon Sep 17 00:00:00 2001
+From: Phil Elwell 
+Date: Tue, 16 Feb 2016 16:40:46 +
+Subject: [PATCH 1/4] bcm43xx: Add bcm43xx-3wire variant
+
+---
+ tools/hciattach.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/tools/hciattach.c b/tools/hciattach.c
+index 59a76a7..5861d33 100644
+--- a/tools/hciattach.c
 b/tools/hciattach.c
+@@ -1144,6 +1144,9 @@ struct uart_t uart[] = {
+   { "bcm43xx",0x, 0x, HCI_UART_H4,   115200, 300,
+   FLOW_CTL, DISABLE_PM, NULL, bcm43xx, NULL  },
+ 
++  { "bcm43xx-3wire",0x, 0x, HCI_UART_3WIRE, 115200, 300,
++  0, DISABLE_PM, NULL, bcm43xx, NULL  },
++
+   { "ath3k",0x, 0x, HCI_UART_ATH3K, 115200, 115200,
+   FLOW_CTL, DISABLE_PM, NULL, ath3k_ps, ath3k_pm  },
+ 
+-- 
+1.9.1
+
diff --git 
a/recipes-connectivity/bluez5/bluez5/0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
 
b/recipes-connectivity/bluez5/bluez5/0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
new file mode 100644
index 000..5a0a434
--- /dev/null
+++ 
b/recipes-connectivity/bluez5/bluez5/0002-bcm43xx-The-UART-speed-must-be-reset-after-the-firmw.patch
@@ -0,0 +1,37 @@
+From e145c9621f976063e5c573db1f2053d906f63427 Mon Sep 17 00:00:00 2001
+From: Phil Elwell 
+Date: Tue, 16 Feb 2016 16:39:09 +
+Subject: [PATCH 2/4] bcm43xx: The UART speed must be reset after the firmware 
download
+
+---
+ tools/hciattach_bcm43xx.c | 6 ++
+ 1 file changed, 2 insertions(+), 4 deletions(-)
+
+diff --git a/tools/hciattach_bcm43xx.c b/tools/hciattach_bcm43xx.c
+index 81f38cb..0b792e0 100644
+--- a/tools/hciattach_bcm43xx.c
 b/tools/hciattach_bcm43xx.c
+@@ -366,11 +366,8 @@ int bcm43xx_init(int fd, int def_speed, int speed, struct 
termios *ti,
+   return -1;
+ 
+   if (bcm43xx_locate_patch(FIRMWARE_DIR, chip_name, fw_path)) {
+-  fprintf(stderr, "Patch not foun

[yocto] [meta-raspberrypi][PATCH 3/5] packagegroup-rpi-test: Add packages to be able to test WiFi/Bluetooth

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 recipes-core/packagegroups/packagegroup-rpi-test.bb | 5 +
 1 file changed, 5 insertions(+)

diff --git a/recipes-core/packagegroups/packagegroup-rpi-test.bb 
b/recipes-core/packagegroups/packagegroup-rpi-test.bb
index f33c05d..ae16cec 100644
--- a/recipes-core/packagegroups/packagegroup-rpi-test.bb
+++ b/recipes-core/packagegroups/packagegroup-rpi-test.bb
@@ -13,10 +13,15 @@ RDEPENDS_${PN} = "\
 pi-blaster \
 python-rtimu \
 python-sense-hat \
+connman \
+connman-client \
+crda \
+bluez5 \
 "
 
 RRECOMMENDS_${PN} = "\
 bigbuckbunny-1080p \
 bigbuckbunny-480p \
 bigbuckbunny-720p \
+${MACHINE_EXTRA_RRECOMMENDS} \
 "
-- 
2.8.0

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

[yocto] [meta-raspberrypi][PATCH 2/5] linux-raspberrypi: Set baudrate and use serial0 for kgdboc

[Andrei Gherzan]

The driver for 8250 defaults to 9600. We setup it on 115200 to be consistent
with getty configuration.

The firmware can do its magic with kgdboc too as it searches and replaces
=serial0 and =serial1. So, use serial0 for kgdboc too.

Signed-off-by: Andrei Gherzan 
---
 recipes-kernel/linux/linux-raspberrypi.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc
index eccbbc6..4799c74 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -20,10 +20,10 @@ KERNEL_DEFCONFIG_raspberrypi ?= "bcmrpi_defconfig"
 KERNEL_DEFCONFIG_raspberrypi2 ?= "bcm2709_defconfig"
 
 # CMDLINE for raspberrypi
-CMDLINE = "dwc_otg.lpm_enable=0 console=serial0 root=/dev/mmcblk0p2 
rootfstype=ext4 rootwait"
+CMDLINE = "dwc_otg.lpm_enable=0 console=serial0,115200 root=/dev/mmcblk0p2 
rootfstype=ext4 rootwait"
 
 # Add the kernel debugger over console kernel command line option if enabled
-CMDLINE_append = ' ${@base_conditional("ENABLE_KGDB", "1", 
"kgdboc=ttyAMA0,115200", "", d)}'
+CMDLINE_append = ' ${@base_conditional("ENABLE_KGDB", "1", 
"kgdboc=serial0,115200", "", d)}'
 
 UDEV_GE_141 ?= "1"
 
-- 
2.8.0

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

[yocto] [meta-raspberrypi][PATCH 1/5] linux-raspberrypi: Bump to v4.4.7

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 recipes-kernel/linux/linux-raspberrypi_4.4.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.4.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
index 8e4530f..9cb8aae 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.4.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.4.bb
@@ -1,8 +1,8 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
 
-LINUX_VERSION ?= "4.4.6"
+LINUX_VERSION ?= "4.4.7"
 
-SRCREV = "2faaa2ccef9e4c595bd26f14285c225ceea6097e"
+SRCREV = "3de232825c9ba5989522b8691eb6ac5df6619458"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.4.y \
file://0001-dts-add-overlay-for-pitft22.patch \
 "
-- 
2.8.0

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

Re: [yocto] [meta-chip][PATCH] u-boot-chip: fix md5sum

[Trevor Woerner]

ping?

(this is needed to build successfully)

On Mon 2016-04-11 @ 02:28:30 PM, Trevor Woerner wrote:
> The u-boot master and chip/stable branches have diverged such that the md5sums
> of the License README files are now different. The latest master branch has
> added a "SIL OPEN FONT LICENSE (OFL-1.1)" license.
> 
> diff:
>   --- chip/stable-README  2016-04-10 02:05:30.783023170 -0400
>   +++ upstream-README 2016-04-11 13:48:34.973027406 -0400
>   @@ -67,4 +67,5 @@
>IBM PIBS (PowerPC Initialization and   IBM-pibs
> ibm-pibs.txt
>   Boot Software) license
>ISC LicenseISC Y   
> isc.txt https://spdx.org/licenses/ISC
>   +SIL OPEN FONT LICENSE (OFL-1.1)OFL-1.1 Y   
> OFL.txt https://spdx.org/licenses/OFL-1.1.html
>X11 LicenseX11 
> x11.txt https://spdx.org/licenses/X11.html
> 
> Signed-off-by: Trevor Woerner 
> ---
>  recipes-bsp/u-boot/u-boot-chip_git.bb | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/recipes-bsp/u-boot/u-boot-chip_git.bb 
> b/recipes-bsp/u-boot/u-boot-chip_git.bb
> index 2342478..60db3e0 100644
> --- a/recipes-bsp/u-boot/u-boot-chip_git.bb
> +++ b/recipes-bsp/u-boot/u-boot-chip_git.bb
> @@ -2,6 +2,8 @@ require recipes-bsp/u-boot/u-boot.inc
>  
>  DESCRIPTION = "U-Boot port for C.H.I.P. boards"
>  
> +LIC_FILES_CHKSUM = 
> "file://Licenses/README;md5=0507cd7da8e7ad6d6701926ec9b84c95"
> +
>  DEPENDS += "dtc-native"
>  PROVIDES += "u-boot"
>  
> -- 
> 2.7.0.rc3
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] udev-cache problems

[Maxim Osipov]

Hi all,

I've a poky/Yocto 1.8 system for an imx6 board equipped with U-Blox SARA-U2
GSM/GPRS module connected via USB. The modem is seen as
several /dev/ttyACM* devices. I use ofono 1.16 to work with the modem.
After startup ofono doesn't detect the modem - it starts
to identify the modem if I restart manually udev daemon (by calling
/etc/init.d/udev restart).
Problem with ofono modem detection during startup disappears if I disable
udev-cache in /etc/default/udev-cache:
by commenting out DEVCACHE variable.

So I've analyzed /etc/init.d/udev and udev-cache scripts.
In my opinion the udev script has problems:

* One funny thing appears during system startup.
First udev computes system configuration and compares it with cached one.
And they are identical! So udev decides that its cache is correct and sets
the flag not_first_boot which leads to call of udevadm command with a lot
of --subsystem-nomatch options (option '--subsystem-nomatch=tty' causes
problems with ofono detection of ttyACM*). But during script execution it
seems that system configuration changes (have a look at trace below - it
seems that /dev/ttyACM* appear after system configuration computation).

*) Ok. Let's restart udev manually. Now udev detects that stored udev-cache
is not correct and it creates file /dev/shm/udev-regen as a flag to
regenerate the cache. But it will be regenerated during subsequent call of
/etc/init.d/udev (it calls internally /etc/init.d/udev-cache script).
Definitely, in case of HW (cold) reboot this flag will disappear,
so as a result /etc/udev-cache.tar.gz file will not be regenerated.

Is there any fix solving properly described problems (except workarounds
like disabling udev-cache or removal of option --subsystem-nomatch=tty from
'udevadm trigger --action=add' call)?

Kind regards,
Maxim.

usb 1-1.3: new high-speed USB device number 3 using ci_hdrc
+ export TZ=/etc/localtime
+ TZ=/etc/localtime
+ '[' -d /sys/class ']'
+ '[' -r /proc/mounts ']'
+ '[' -x /lib/udev/udevd ']'
+ SYSCONF_CACHED=/etc/udev/cache.data
+ SYSCONF_TMP=/dev/shm/udev.cache
+ DEVCACHE_REGEN=/dev/shm/udev-regen
+ CMP_FILE_LIST='/proc/version /proc/cmdline /proc/devices'
+ '[' -f /proc/atags ']'
+ META_FILE_LIST='lib/udev/rules.d/* etc/udev/rules.d/*'
+ '[' -f /etc/default/udev-cache ']'
+ . /etc/default/udev-cache
++ DEVCACHE=/etc/udev-cache.tar.gz
++ PROBE_PLATFORM_BUS=yes
+ '[' -f /etc/udev/udev.conf ']'
+ . /etc/udev/udev.conf
++ udev_run=/var/run/udev
+ '[' -f /etc/default/rcS ']'
+ . /etc/default/rcS
++ TMPTIME=0
++ SULOGIN=no
++ DELAYLOGIN=no
++ UTC=yes
++ VERBOSE=no
++ EDITMOTD=no
++ ENABLE_ROOTFS_FSCK=no
++ FSCKFIX=yes
++ VOLATILE_ENABLE_CACHE=yes
++ ROOTFS_READ_ONLY=no
+ case "$1" in
+cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
export ACTION=add
+ ACTION=add
+ echo 'Starting udev'
Startincdc_acm 1-1.3:1.2: ttyACM1: USB ACM device
g udev
+ grep -q devtmpfs /proc/filesystems
+ LANG=C
+ awk '$2 == "/dev" && ($3 == "devtmpfs")cdc_acm 1-1.3:1.4: ttyACM2: USB
ACM device
{ exit 1 }' /proc/mounts
+ '[' -e /dev/pts ']'
+ mkdir -m 0755cdc_acm 1-1.3:1.6: ttyACM3: USB ACM device
/dev/pts
+ '[' -e /dev/shm ']'
+ mkdir -m 1777 /dev/shm
+ mkdcdc_acm 1-1.3:1.8: ttyACM4: USB ACM device
ir -m 1777 -p /var/volatile/tmp
+ '[' /etc/udev-cache.tar.gz '!=cdc_acm 1-1.3:1.10: ttyACM5: USB ACM device
' '' ']'
+ '[' -e /etc/udev-cache.tar.gz ']'
+ sysconf_cmd
+ ccdc_acm 1-1.3:1.12: ttyACM6: USB ACM device
at -- /proc/version /proc/cmdline /proc/devices
+ awk -F/ '{print $1 " " $NF;}'
+ stat -c '%s %Y %n' -- lib/udev/rules.d/40-usb_modeswitch.rules
lib/udev/rules.d/42-usb-hid-pm.rules
lib/udev/rules.d/50-udev-default.rules
lib/udev/rules.d/60-cdrom_id.rules lib/udev/rules.d/60-persistent-als2
lib/udev/rules.d/75-tty-description.rules
lib/udev/rules.d/78-sound-card.rules lib/udev/rules.d/80-drivers.rules
lib/udev/rules.d/85-regulatory.rules
lib/udev/rules.d/95-keyboard-force-release.rules lib/udev/rus
+ cmp /etc/udev/cache.data /dev/shm/udev.cache
+ tar xmf /etc/udev-cache.tar.gz -C / -m
+ not_first_boot=1
+ '[' no '!=' no ']'
+ '[' -e /dev/shm/udev.cache ']'
+ rm -f /dev/shm/udev.cache
+ '[' -e /dev/shm/udev-regen ']'
+ kill_udevd
+ '[' -e /proc/sys/kernel/hotplug ']'
+ echo -e '\000'
+ /lib/udev/udevd -d
+ udevadm control --env=STARTUP=1
+ '[' 1 '!=' '' ']'
+ '[' yes '!=' yes ']'
+ PLATFORM_BUS_NOMATCH=
+ udevadm trigger --action=add --subsystem-nomatch=tty
--subsystem-nomatch=mem --subsystem-nomatch=vc
--subsystem-nomatch=vtconsole --subsystem-nomatch=misc
--subsystem-nomatch=dcon --subsystem-nomatch=pci_bus x
+ exit 0
+ udevadm settle --timeout=3
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH V2 1/4] firmware.inc: Update firmware to include various serial fixes

[Andrei Gherzan]

On Thu, Apr 21, 2016 at 08:42:36PM +0100, Theodor Gherzan wrote:
> From: Theodor Gherzan 
>
> Signed-off-by: Theodor Gherzan 
> ---
>  recipes-bsp/common/firmware.inc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc
> index c1117d6..abc7d06 100644
> --- a/recipes-bsp/common/firmware.inc
> +++ b/recipes-bsp/common/firmware.inc
> @@ -1,5 +1,5 @@
> -RPIFW_SRCREV ?= "046effa13ebc4cc7601df4f06f4834bd0eebb0f8"
> -RPIFW_DATE ?= "20160326"
> +RPIFW_SRCREV ?= "c5e131971c323f5658c7c5d4b1dd105d37903a99"
> +RPIFW_DATE ?= "20160303"
>  RPIFW_SRC_URI ?= 
> "git://github.com/raspberrypi/firmware.git;protocol=git;branch=master"
>  RPIFW_S ?= "${WORKDIR}/git"

Merged to master (along with the other patches in the series). Thanks.
Some minor modifications added (README).

--
Andrei Gherzan


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

Re: [yocto] [psplash][PATCH] psplash: add option to read startup message from file

[Richard Leitner]

Hi,
are any comments or possible improvements?
On 04/15/2016 10:49 AM, Richard Leitner wrote:
> This patch adds an option to read the displayed message from a file.
> Additionally the maximum length for the read string can be defined.
> If both, a message (STARTUP_MSG) and a file (STARTUP_MSG_FILE) are
> defined the content of the file will be appended to the message.
> The string will be cutted after the given maximum number of chars.
> 
> For these changes the following defines were introduced:
>   PSPLASH_STARTUP_MSG_MAX_LEN ... maximum lenght of the complete message
>   PSPLASH_STARTUP_MSG_FILE .. path to the file to read

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