Re: [yocto] QA cycle report for 2.4 M2 rc2

[Richard Purdie]

On Wed, 2017-08-02 at 17:55 -0700, Cruz, Libertad wrote:
> QA does not approve that  the workarounds provided  for 2.4 m2 rc2
>  were on different commits. Testing was not limited to 2.4 m2 rc2
> commit “8e15e9b6e478f6368034519b2a8fd3c7ea71d23b” it was performed by
> following each commit on the provided workarounds described below.  

Thanks Libertad.

The different commits wasn't intentional, there were bugs which were
reported and fixed after rc2 was built. It made sense to resolve those
bugs as fixed in master but obviously they were still present in M2.

Given the high volume of issues and other things that went on with rc2
I've decided to build an rc3. We'll have to take current master as
there are some many fixes it only makes sense to use that rather than
create any special branch. I've set that build away.

Cheers,

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

[yocto] Mplayer how to?

[Riko Ho]

Dear Yocto Team Member,

How can I add mplayer to my image?

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

Re: [yocto] bitbake download only

[Burton, Ross]

Yes,

bitbake core-image-minimal -c fetchall

Ross

On 3 August 2017 at 15:55, blackthirt33n .  wrote:

> Is it possible to perform a download only bitbake of a recipe/target?
>
> For instance only download the necessary files for core-image-minimal?
>
> James
>
> --
> ___
> 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] Release Candidate Build for yocto-2.4_M2.rc3 now available.

[Poky Build User]

A release candidate build for yocto-2.4_M2.rc3 is now available at:


https://autobuilder.yocto.io/pub/releases/yocto-2.4_M2.rc3


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : 0d590c4be300365a2d1787fcea767ac41c741875 
meta-qt4 : d52c38ad9f0a617b9ad5048a872a9e97b3af5b44 
refkit : 112c0e10de6414657f097671005bc21adabf381b 
meta-mingw : 0679d2a91575bd7f3efd0973aa99d7ee681e9395 
meta-qt3 : f33b73a9563f2dfdfd0ee37b61d65d90197a456f 
meta-gplv2 : 07e5dd2136a2a7cc069ad8c70bb422fa9d5b14f0 
poky : 9ed748a542b520c1cb763d981969233c0f5efd4e 

\nThis is an automated message from\nThe Yocto Project Autobuilder\nGit: 
git://git.yoctoproject.org/yocto-autobuilder\nEmail: pi...@toganlabs.com 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] bitbake download only

[Burton, Ross]

On 3 August 2017 at 17:00, Matthew McClintock 
wrote:

> On Thu, Aug 3, 2017 at 10:00 AM, Burton, Ross 
> wrote:
> > Yes,
> >
> > bitbake core-image-minimal -c fetchall
>
> Or for more recent version of bitbake
>
> bitbake core-image-minimal --runall fetch


I'd actually forgotten that existed.  Maybe fetchall should tell the user?

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

[yocto] bitbake download only

[blackthirt33n .]

Is it possible to perform a download only bitbake of a recipe/target?

For instance only download the necessary files for core-image-minimal?

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

Re: [yocto] bitbake download only

[Matthew McClintock]

On Thu, Aug 3, 2017 at 10:00 AM, Burton, Ross  wrote:
> Yes,
>
> bitbake core-image-minimal -c fetchall

Or for more recent version of bitbake

bitbake core-image-minimal --runall fetch

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

[yocto] [meta-cgl][PATCH] corosync: update to 1.4.8

[jackie.huang]

From: Jackie Huang 

- Add systemd support
- Add PACKAGECONFIG for nss, dbus, rdma and snmp
- Install config file for corosync-notifyd

Signed-off-by: Jackie Huang 
---
 .../corosync/corosync/corosync-notifyd.service | 13 +++
 .../recipes-cgl/corosync/corosync/corosync.service | 26 ++
 .../{corosync_1.4.7.bb => corosync_1.4.8.bb}   | 42 ++
 3 files changed, 74 insertions(+), 7 deletions(-)
 create mode 100644 
meta-cgl-common/recipes-cgl/corosync/corosync/corosync-notifyd.service
 create mode 100644 
meta-cgl-common/recipes-cgl/corosync/corosync/corosync.service
 rename meta-cgl-common/recipes-cgl/corosync/{corosync_1.4.7.bb => 
corosync_1.4.8.bb} (51%)

diff --git 
a/meta-cgl-common/recipes-cgl/corosync/corosync/corosync-notifyd.service 
b/meta-cgl-common/recipes-cgl/corosync/corosync/corosync-notifyd.service
new file mode 100644
index 000..ce576fe
--- /dev/null
+++ b/meta-cgl-common/recipes-cgl/corosync/corosync/corosync-notifyd.service
@@ -0,0 +1,13 @@
+[Unit]
+Description=Corosync Dbus and snmp notifier
+Wants=corosync.service
+After=corosync.service
+
+[Service]
+EnvironmentFile=@SYSCONFDIR@/sysconfig/corosync-notifyd
+ExecStart=@SBINDIR@/corosync-notifyd -f $OPTIONS
+Type=simple
+Restart=on-failure
+
+[Install]
+WantedBy=multi-user.target
diff --git a/meta-cgl-common/recipes-cgl/corosync/corosync/corosync.service 
b/meta-cgl-common/recipes-cgl/corosync/corosync/corosync.service
new file mode 100644
index 000..d5dd38f
--- /dev/null
+++ b/meta-cgl-common/recipes-cgl/corosync/corosync/corosync.service
@@ -0,0 +1,26 @@
+[Unit]
+Description=Corosync Cluster Engine
+ConditionKernelCommandLine=!nocluster
+Requires=network-online.target
+After=network-online.target
+
+[Service]
+ExecStart=@DATADIR@/corosync/corosync start
+ExecStop=@DATADIR@/corosync/corosync stop
+Type=oneshot
+RemainAfterExit=yes
+
+# The following config is for corosync with enabled watchdog service.
+#
+#  When corosync watchdog service is being enabled and using with
+#  pacemaker.service, and if you want to exert the watchdog when a
+#  corosync process is terminated abnormally,
+#  uncomment the line of the following Restart= and RestartSec=.
+#Restart=on-failure
+#  Specify a period longer than soft_margin as RestartSec.
+#RestartSec=70
+#  rewrite according to environment.
+#ExecStartPre=/sbin/modprobe softdog soft_margin=60
+
+[Install]
+WantedBy=multi-user.target
diff --git a/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.7.bb 
b/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.8.bb
similarity index 51%
rename from meta-cgl-common/recipes-cgl/corosync/corosync_1.4.7.bb
rename to meta-cgl-common/recipes-cgl/corosync/corosync_1.4.8.bb
index 019a2f4..3b5afce 100644
--- a/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.7.bb
+++ b/meta-cgl-common/recipes-cgl/corosync/corosync_1.4.8.bb
@@ -4,7 +4,7 @@ several default APIs and libraries, default configuration 
files, and an init \
 script."
 HOMEPAGE = "http://corosync.github.io/corosync/;
 
-inherit autotools pkgconfig update-rc.d useradd
+inherit autotools pkgconfig update-rc.d useradd systemd
 
 SRC_URI = "http://build.clusterlabs.org/corosync/releases/${BPN}-${PV}.tar.gz \
file://groff-desc-path.patch \
@@ -13,22 +13,29 @@ SRC_URI = 
"http://build.clusterlabs.org/corosync/releases/${BPN}-${PV}.tar.gz \
file://build-cleanup-configure-ac.patch \
file://corosync.init \
file://notifyd.init \
+   file://corosync.service \
+   file://corosync-notifyd.service \
file://volatiles \
   "
 
-SRC_URI[md5sum] = "da9b2cf0b55f08ac4cf7cd82ac2f977a"
-SRC_URI[sha256sum] = 
"c1d005b2093e9a725abd1dfb2be936114b561c0b3145aca11f58c1a733a05af8"
+SRC_URI[md5sum] = "e16c71db45c8b39948847655958d0dec"
+SRC_URI[sha256sum] = 
"64ee50f783a4bfa8a63fd576090cf7dd1810f3c60e01b4886723b87c5ff2b013"
 
 LICENSE = "BSD"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=25656171d1e4054c636a9893067f8c30"
 
-DEPENDS = "groff-native nss"
+DEPENDS = "groff-native"
 
 INSANE_SKIP_${PN} += ""
 
-EXTRA_OECONF += " --enable-nss "
 CFLAGS_append += " -fPIC "
 
+PACKAGECONFIG ?= "dbus nss snmp"
+PACKAGECONFIG[dbus] = "--enable-dbus,--disable-dbus,dbus"
+PACKAGECONFIG[nss] = "--enable-nss,--disable-nss,nss"
+PACKAGECONFIG[rdma] = "--enable-rdma,--disable-rdma"
+PACKAGECONFIG[snmp] = "--enable-snmp,--disable-snmp,net-snmp"
+
 do_compile() {
 DESCPATH="${STAGING_DATADIR_NATIVE}/groff/`groff -v | awk '{if(NR==1)print 
$4}'`/font"
 oe_runmake DESCPATH=${DESCPATH}
@@ -37,6 +44,7 @@ do_compile() {
 do_install_append() {
 install -d ${D}${sysconfdir}/default/volatiles
 install -m 0644 ${WORKDIR}/volatiles 
${D}${sysconfdir}/default/volatiles/05_corosync
+install -D -m 0644 ${S}/tools/corosync-notifyd.sysconfig.example 
${D}${sysconfdir}/sysconfig/corosync-notifyd
 
 # Original init script is too bashy
 rm -f 

[yocto] meta-kodi questions ?

[Riko Ho]

Dear Yocto Team Member,

I want to build my image with meta-kodi for beagle but I got this issue :

==

ERROR: libffi-native-3.2.1-r0 do_configure: Function failed: 
do_configure (log file is located at 
/home/bianchi77/poky/build/tmp/work/x86_64-linux/libffi-native/3.2.1-r0/temp/log.do_configure.15177)
ERROR: Logfile of failure stored in: 
/home/bianchi77/poky/build/tmp/work/x86_64-linux/libffi-native/3.2.1-r0/temp/log.do_configure.15177

Log data follows:
| DEBUG: Executing shell function autotools_preconfigure
| DEBUG: Shell function autotools_preconfigure finished
| DEBUG: Executing python function autotools_aclocals
| DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 
'bit-64', 'x86_64-linux', 'common']

| DEBUG: Python function autotools_aclocals finished
| DEBUG: Executing shell function do_configure
| Unescaped left brace in regex is illegal here in regex; marked by <-- 
HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at 
/home/bianchi77/poky/build/tmp/work/x86_64-linux/libffi-native/3.2.1-r0/recipe-sysroot-native/usr/bin/automake 
line 3940.
| Unescaped left brace in regex is illegal here in regex; marked by <-- 
HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at 
/home/bianchi77/poky/build/tmp/work/x86_64-linux/libffi-native/3.2.1-r0/recipe-sysroot-native/usr/bin/automake 
line 3940.

| WARNING: exit code 255 from a shell command.

=

Does anyone know any ideas about it ?

Thanks,

--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

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

Re: [linux-yocto] [PATCH 00/15] Intel Axxia updates to linux-yocto-4.1

[Bruce Ashfield]

On 08/02/2017 08:46 AM, Daniel Dragomir wrote:

Hello Bruce!

Please review and merge this series of patches in Axxia branches from
linux-yocto-4.1.
Changes included in this series (axxia tags: 1.61-1.63):

Linux 1.61 Changes
- Rebase from 4.1.39 to 4.1.42.
- Fix warnings introduced by the rebased mentioned above.
- Add tracing of NCR, PEI, and PCI accesses. Tracing can be enabled
   using the bootargs or after booting using /sys.
- For NCR, use trace for all accesses, and trace_value_read
   to display the value read after a read.
 - For PEI and PCI, use trace.
- PCI Updates.
- Add a work around for a hardware problem. If the link is
   not established at the requested number of lanes, reduce
   and try again. If there is no link at x1, fail.
- Update the LOS work around to work the the lane reduction
   work around mentioned above.
- Add a new configuration for 5600, unsupported on the Axxia
   development board, configuration 5.
 - In configuration 2, 5600, set sw_port_1 to 0x2 instead of 0x4.
 - Always set the number of phys to 4 for 5600 and 1 for 6700.
 - Always set the link width speed change register to x1 and use
   the link control register to set the desired width.
- USB Updates and USB support for 5600 B* parts.
- Use HCRST for soft resets in the driver and don't reset the
   PHY seperately sinc HCRST resets the PHY.
- Move all changes to constant values to the early init code
   (SPL) instead of the driver.

Linux 1.62 Changes
- Fix a boot problem on 5500. In the new Axxia fault code, exceptions
   need to be masked on 5500 by default.
- The final change to the PCI work around (If the link is not established
   at the requested number of lanes...) was not included. As the hardware
   does not have the correct default class code, software needs to set it.
   With the width change work around, the class code needs to be set to the
   correct value each time the width is changed.
- Update the default configurations to get rid of some warnings when using
   systemd instead of sysv init.

Linux 1.63 Changes
- Update USB to use the original reset sequence instead of asserting HCRST.
   The HCRST reset breaks USB2 and USB3 in some cases.
- Fixes for PEI configuration 5.


If all the patches are ok, please pull them from
https://github.com/axxia/axxia_yocto_linux_4.1_pull.git
into
git://git.yoctoproject.org/linux-yocto-4.1
Pull
standard/axxia/base-1.63 -> standard/axxia/base
standard/preempt-rt/axxia/base-1.63 -> standard/preempt-rt/axxia/base

If you add more patches to standard/(preempt-rt)/axxia/base beforehand
please notify me. I will rebase our changes so you can do a clean,
fast-forward pull.


These looked fine to me, and are now merged.

Bruce



Thank you,
Daniel Dragomir

Charlie Paul (1):
   drivers/usb/dwc3: Support for Axxia USB-B0 added

John Jacques (14):
   drivers/pci: Axxia Hardware Work Around
   drivers/misc: Update Axxia PEI Configuration
   drivers/pci: Work Around an Axxia Hardware Problem
   drivers/misc: Add a New Axxia Configuration
   drivers/pci: Work Around a Hardware Defect on Axxia
   drivers/pci: Update the Axxia PCIe LOS Work Around
   drivers/misc: Update NCR Tracing on Axxia
   drivers/misc: Update PEI Logging on Axxia
   drivers/pci: Update Tracing in the Axxia PCI Driver
   drivers/of: Fix Compile Warning
   drivers/misc: Update the Axxia Fault Handler
   drivers/pci: Axxia Hardware Work Around
   drivers/misc: Update the Axxia PEI Driver
   drivers/usb: Updated Axxia DWC3 Driver

  arch/arm64/boot/dts/intel/axc67xx.dtsi |   4 -
  arch/arm64/boot/dts/intel/axm56xx.dtsi |   1 -
  drivers/misc/axxia-fault.c |   1 +
  drivers/misc/axxia-pei.c   | 545 +---
  drivers/misc/lsi-ncr.c | 103 --
  drivers/of/fdt.c   |   2 +-
  drivers/pci/host/pcie-axxia.c  | 555 +++--
  drivers/pci/host/pcie-axxia.h  |   1 +
  drivers/usb/dwc3/Makefile  |   1 -
  drivers/usb/dwc3/core.c|  10 -
  drivers/usb/dwc3/core.h|   6 -
  include/linux/axxia-pei.h  |   1 +
  12 files changed, 1029 insertions(+), 201 deletions(-)



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