[yocto] [Recipe reporting system] Upgradable recipe name list

[recipe-report]

This mail was sent out by Recipe reporting system.

This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version was detected.

Example:
RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable"

You can check the detail information at:

http://recipes.yoctoproject.org/

Package   VersionUpstream version  Maintainer   
NoUpgradeReason
  -    ---  
--
perl  5.22.1 5.24.0Alejandro Hernandez
texinfo   6.06.1   Alejandro Hernandez
python3   3.5.1  3.5.2 Alejandro Hernandez
python-native 2.7.11 2.7.12Alejandro Hernandez
python3-git   1.0.2  2.0.6 Alejandro Hernandez
cronie1.5.0  1.5.1 Alejandro Hernandez
swig  3.0.8  3.0.10Alejandro Hernandez
python-git2.0.5  2.0.6 Alejandro Hernandez
python3-setuptools22.0.5 24.0.1Alejandro Hernandez
python-setuptools 22.0.5 24.0.1Alejandro Hernandez
perl-native   5.22.1 5.24.0Alejandro Hernandez
python3-native3.5.1  3.5.2 Alejandro Hernandez
python2.7.11 2.7.12Alejandro Hernandez
liberation-fonts  1.04   2.00.1Alexander Kanavin
2.x depends on fontforge pa...
bdwgc 7.4.2  7.4.4 Alexander Kanavin
vala  0.30.1 0.32.1Alexander Kanavin
epiphany  3.18.4 3.20.3Alexander Kanavin
libwnck3  3.14.1 3.20.1Alexander Kanavin
nss   3.23   3.24  Alexander Kanavin
libarchive3.2.0  3.2.1 Alexander Kanavin
gnutls3.4.11 3.5.1 Alexander Kanavin
ffmpeg3.0.2  3.1.1 Alexander Kanavin
bash-completion   2.12.3   Alexander Kanavin
btrfs-tools   4.5.3  4.6.1 Alexander Kanavin
mpg1231.23.4 1.23.6Alexander Kanavin
babeltrace1.3.2  1.4.0 Alexander Kanavin
mkelfimage4.0+gitX   4.4+gitAUTOINC+58...  Alexander Kanavin
mkelfimage has been removed...
desktop-file-util...  0.22   0.23  Alexander Kanavin
apt   1.0.10.1   1.2.14Aníbal Limón
apt-native1.0.10.1   1.2.14Aníbal Limón
pinentry  0.9.2  0.9.7 Armin Kuster
linux-libc-headers4.44.6.3 Bruce Ashfield
guilt-native  0.35+gitX  0.36+gitAUTOINC+2...  Bruce Ashfield
at3.1.18 3.1.20Chen Qi
byacc 20160324   20160606  Chen Qi
cups  2.1.3  2.1.4 Chen Qi
sudo  1.8.16 1.8.17p1  Chen Qi
sysstat   11.3.4 11.3.5Chen Qi
u-boot-fw-utils   v2016.03+gitX  v2016.05+gitAUTOI...  Denys Dmytriyenko
u-boot-mkimagev2016.03+gitX  v2016.05+gitAUTOI...  Denys Dmytriyenko
u-bootv2016.03+gitX  v2016.05+gitAUTOI...  Denys Dmytriyenko
createrepo0.4.11 0.10.4Hongxu Jia   
Versions after 0.9.* use YU...
ncurses   6.0+20160319   6.0+20160625  Hongxu Jia
libgcrypt 1.7.0  1.7.1 Hongxu Jia
gnupg 2.1.12 2.1.13Hongxu Jia
libinput  1.3.0  1.3.3 Jussi Kukkonen
weston1.10.0 1.11.0Jussi Kukkonen
matchbox-config-gtk   0.22 Jussi Kukkonen
matchbox-terminal 0.12 Jussi Kukkonen
sato-screenshot   0.22 Jussi Kukkonen
settings-daemon   0.0.2  2 Jussi Kukkonen
xf86-input-evdev  2.10.2 2.10.3Jussi Kukkonen
xf86-input-synaptics  1.8.3  1.8.99.1  Jussi Kukkonen
matchbox-theme-sato   0.22 Jussi Kukkonen
sgmlspl-native1.1+gitX   1.03+gitAUTOINC+f...  Jussi Kukkonen
wayland   1.10.0 1.11.0Jussi Kukkonen
libevdev 

Re: [linux-yocto] [PATCH 0/5] Intel Axxia updates to linux-yocto-4.1

[Bruce Ashfield]

On 2016-07-01 8:37 AM, Daniel Dragomir wrote:

Hello Bruce!

This series of patches brings improvements for USB, PCI AND NETWORK
drivers and add some features in Victoria board Device Tree.

NOTE: All the following patches are for both axxia branches:
standard/axxia/base and standard/preempt-rt/axxia/base,


Thanks. I've staged the changes

Bruce



Axxia internal tag: 1.33

Thank you,
Daniel Dragomir

John Jacques (5):
  axxia: PCI Updates for 5600 Hardware
  board/axxia: SPI Updates for Victoria
  axxia: Add USB to the Victoria Device Tree
  drivers/usb: Make Axxia USB Use Coherent Memory for DMA
  drivers/net: Disable Pause Frames in the Axxia Network Interface

 arch/arm64/boot/dts/intel/axm5616-victoria.dts | 53 +-
 arch/arm64/boot/dts/intel/axm56xx.dtsi |  2 +-
 drivers/net/ethernet/intel/axxia/nemac.c   | 17 +++--
 drivers/pci/host/pcie-axxia.c  | 36 +++--
 drivers/usb/dwc3/dwc3-axxia.c  | 14 +++
 5 files changed, 97 insertions(+), 25 deletions(-)



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

Re: [linux-yocto] [PATCH] mei.cfg: Add CONFIG_INTEL_MEI_TXE=m

[Bruce Ashfield]

On 2016-06-30 5:15 PM, Saul Wold wrote:

This will create the TXE based Intel Management Excution Interface
to support additional chipsets.


merged to 4.1, 4.4, 4.6 and master

Bruce



Signed-off-by: Saul Wold 
---
 features/amt/mei/mei.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/features/amt/mei/mei.cfg b/features/amt/mei/mei.cfg
index 3195218..de6f657 100644
--- a/features/amt/mei/mei.cfg
+++ b/features/amt/mei/mei.cfg
@@ -2,3 +2,4 @@ CONFIG_STAGING=y
 CONFIG_WATCHDOG_CORE=y
 CONFIG_INTEL_MEI=m
 CONFIG_INTEL_MEI_ME=m
+CONFIG_INTEL_MEI_TXE=m



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

Re: [linux-yocto] [PATCH 0/7] USB Type C backport on linux-yocto-4.4 bxt-rebase branch

[Bruce Ashfield]

On 2016-06-29 5:50 PM, Pranav Tipnis wrote:

This patch set backports USB Type C support on linux-yocto-4.4
from kernel version 4.7-rc. These patches have been submitted
upstream and the approval is in progress, hence may not be
final. The patches have been rebased on bxt-rebase branch.


Some portion of these are already on bxt-rebase.

Can you refresh from git.yoctoproject.org and re-submit
anything that is missing from standard/intel/bxt-rebase ?

Bruce



Bin Gao (2):
  acpi/pmic: modify the pen function signature to take bit field
  acpi/pmic: Add opregion driver for Intel BXT WhiskeyCove PMIC

Felipe Balbi (1):
  acpi/pmic: Add support for PMIC regs operation region

Pranav Tipnis (4):
  usb: USB Type-C connector class
  usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY
  mfd: intel_soc_pmic_bxtwc: Add Intel BXT WhiskeyCove PMIC ADC thermal
channel mapping and USB type-C resources
  usb: typec: Use strtobool instead of kstrtobool for 4.4 kernel

 Documentation/ABI/testing/sysfs-class-typec |  236 +
 Documentation/usb/typec.txt |  103 +++
 MAINTAINERS |9 +
 drivers/acpi/Kconfig|6 +
 drivers/acpi/Makefile   |1 +
 drivers/acpi/pmic/intel_pmic.c  |   82 +-
 drivers/acpi/pmic/intel_pmic.h  |4 +-
 drivers/acpi/pmic/intel_pmic_bxtwc.c|  424 +
 drivers/acpi/pmic/intel_pmic_crc.c  |5 +-
 drivers/mfd/intel_soc_pmic_bxtwc.c  |  126 ++-
 drivers/usb/Kconfig |2 +
 drivers/usb/Makefile|2 +
 drivers/usb/typec/Kconfig   |   21 +
 drivers/usb/typec/Makefile  |2 +
 drivers/usb/typec/typec.c   | 1277 +++
 drivers/usb/typec/typec_wcove.c |  371 
 include/linux/mfd/intel_soc_pmic.h  |   21 +
 include/linux/usb/typec.h   |  260 ++
 18 files changed, 2940 insertions(+), 12 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-class-typec
 create mode 100644 Documentation/usb/typec.txt
 create mode 100644 drivers/acpi/pmic/intel_pmic_bxtwc.c
 create mode 100644 drivers/usb/typec/Kconfig
 create mode 100644 drivers/usb/typec/Makefile
 create mode 100644 drivers/usb/typec/typec.c
 create mode 100644 drivers/usb/typec/typec_wcove.c
 create mode 100644 include/linux/usb/typec.h



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

[yocto] Toaster fail to luanch bitbake

[Richard Zhang]

Hi:



After setup toaster I can't finish build progress with bitbake.







some ERROR log into :



/opt/yocto/poky/build-toaster-4/toaster_ui.log



ERROR: can't set event mask: None





Is this ERROR come with Environment variant?





Thanks.





Richard Zhang

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

Re: [yocto] Xorg failing with SEGV after Krogoth update

[Allan Chandler]

Khem,

I managed to get gdb up and running on the target system by adding 
'tools-debug' to the 'IMAGE_FEATURES' in my top level recipe, executing 'ulimit 
-c unlimited' as you suggested, and running 'Xorg -core'.

I'll start looking into it more deeply but initial investigation seems to 
indicate something has smashed the stack. Loading up the core file for a 
backtrace gives me:

Core was generated by `Xorg -br -pn -nolisten tcp -core'.
Program terminated with signal SIGABRT, Aborted.
#0  0x76afda54 in raise () from /lib/libc.so.6
(gdb) bt
#0  0x76afda54 in raise () from /lib/libc.so.6
#1  0x76afedd0 in abort () from /lib/libc.so.6
#2  0x00183708 in OsAbort ()
#3  0x0007e6c0 in ddxGiveUp ()
#4  0x001887ac in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt 
stack?)

Not _overly_ useful information since, by the time you're in ddxGiveUp, you're 
already well and truly into the abort process. Still, it's a good starting 
point, so I'm appreciative of your assistance.

If anyone else also wants to weigh in with  their advice (or even at least 
relatively intelligent speculation), I'd be grateful.

Cheers,
Al.


-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com] 
Sent: Friday, 1 July 2016 11:02 PM
To: Allan Chandler
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Xorg failing with SEGV after Krogoth update

On Thu, Jun 30, 2016 at 10:24 PM, Allan Chandler  
wrote:
> We recently did (attempted? ) an upgrade of our Yocto embedded build 
> system from Fido to Krogoth and, other than one rather massive issue, 
> it all went well.
>
>
>
> The massive issue is the fact that  X11 is apparently not starting 
> correctly. The embedded device boots okay since we can see in via a 
> serial console as well as connecting via SSH.
>
>
>
> We've narrowed the actual issue down to the Xorg executable, after 
> following the process the the rc5.d Xserver satrtup scripts and xinit 
> - basically, Xorg is dumping core with the following output:
>

may be you can enable coredump and collect it for offline post mortem setting 
ulimit -c unlimited e.g. when you run the suspected program will dump it

>
>
> X.Org X Server 1.18.0
>
> Release Date: 2015-11-09
>
> X Protocol Version 11, Revision 0
>
> Build Operating System: Linux 3.19.0-25-generic x86_64
>
> Current Operating System: Linux imx6 3.14.28+g2b0ab6d #1 SMP 
> PREEMPT Thu Jun 30 12:20:09 AWST 2016 armv7l
>
> Kernel command line: console=ttymxc0,115200 consoleblank=0
> root=/dev/mmcblk3p2 rootwait
>
> Build Date: 30 June 2016  01:38:24PM
>
>
>
> Current version of pixman: 0.32.8
>
> Before reporting problems, check 
> https://linkprotect.cudasvc.com/url?a=http://wiki.x.org=E,1,4NSJpdkB
> 74woeWCSgwq2yLsnPqo_Nw27PMKnrxE-_x_0DAqZF5Z0WYcmV4NJ1-ni3fjHphEzkRgcSt
> 4Gfm-gPUcpYnS2hfj-TM3SeZPx=1
>
> to make sure that you have the latest version.
>
> Markers: (--) probed, (**) from config file, (==) default setting,
>
> (++) from command line, (!!) notice, (II) informational,
>
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>
> (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul  1 00:12:43 
> 2016
>
> (==) Using config file: "/etc/X11/xorg.conf"
>
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>
> (==) No Layout section.  Using the first Screen section.
>
> (==) No screen section available. Using defaults.
>
> (**) |-->Screen "Default Screen Section" (0)
>
> (**) |   |-->Monitor ""
>
> (==) No device specified for screen "Default Screen Section".
>
> Using the first device section listed.
>
> (**) |   |-->Device "i.MX Accelerated Framebuffer Device"
>
> (==) No monitor specified for screen "Default Screen Section".
>
> Using a default monitor configuration.
>
> (**) Option "BlankTime" "0"
>
> (**) Option "StandbyTime" "0"
>
> (**) Option "SuspendTime" "0"
>
> (**) Option "OffTime" "0"
>
> (==) Automatically adding devices
>
> (==) Automatically enabling devices
>
> (==) Automatically adding GPU devices
>
> (==) Max clients allowed: 256, resource mask: 0x1f
>
> (WW) The directory "/usr/share/fonts/X11/misc/" does not exist.
>
> Entry deleted from font path.
>
> (WW) The directory "/usr/share/fonts/X11/TTF/" does not exist.
>
> Entry deleted from font path.
>
> (WW) The directory "/usr/share/fonts/X11/OTF/" does not exist.
>
> Entry deleted from font path.
>
> (WW) The directory "/usr/share/fonts/X11/Type1/" does not exist.
>
> Entry deleted from font path.
>
> (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
>
> Entry deleted from font path.
>
> (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
>
>

[yocto] Poky/MPC8315E-RDB: "preferred version v2013.07% of u-boot not available (for item u-boot)"

[Robert P. J. Day]

  building with current poky for yocto bsp ref board MPC8315E-RDB,
and it still prefers a version of u-boot that is no longer available:

NOTE: Resolving any missing task queue dependencies
NOTE: preferred version v2013.07% of u-boot not available (for item u-boot)
NOTE: versions of u-boot available: v2016.03+gitAUTOINC+df61a74e68
NOTE: preferred version v2013.07% of u-boot not available (for item u-boot)
NOTE: versions of u-boot available: v2016.03+gitAUTOINC+df61a74e68
NOTE: preferred version v2013.07% of u-boot not available (for item u-boot-dev)
NOTE: versions of u-boot available: v2016.03+gitAUTOINC+df61a74e68

Build Configuration:
BB_VERSION= "1.31.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS= "powerpc-poky-linux"
MACHINE   = "mpc8315e-rdb"
DISTRO    = "poky"
DISTRO_VERSION= "2.1+snapshot-20160703"
TUNE_FEATURES = "m32 fpu-hard ppce300c3"
TARGET_FPU= ""
meta
meta-poky
meta-yocto-bsp= "master:5c11e365e19357f721c49d076971567e7b64b61b"

  should i submit a patch that just deletes the PREFERRED_VERSION
line?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


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

[yocto] devtool build fails the second time

[Michael Lausch]

Hi,
I want to use `devtool modify ' to modify the source code and
create patches.  already contains some source patches.

My workflow looks like this:

devtool modity 
Fetching, Unpacking, Patching 
all works

devtool build 


devtool build 
fails during compile task, that's expected and that's the reason i want
to create the patches.

A second
devtool build  
call, immediatly after the first one fails with
do_fetch: Taskhash mismatch 5786499f8bbbc5af0471f764b7796c77 verses
919d46a764e4f9122d53f1b74d37a4b8

The same taskhash error happens for the do_patch task, with different
hash sums.

The do_patch task fails with the error, that the patches have already
been applied. 

what am I doing wrong?

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

[yocto] USB cam - video device numbering

[Peter Balazovic]

Dears,

I have a driver patch for deserializer (MIPI interface cams) which
overwrites /dev/video0 but this is the usual device assigned to the
usb camera via UVC driver. I want both drivers coexist so I want to
change: example, USB camera being /dev/video5 and not video0.

Can I get advice where should I look at and what to change?

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