[yocto] [Recipe reporting system] Upgradable recipe name list
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 this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-xxx in upstream_tracking files to ignore this recipe remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON_pn-xxx = Not upgrade to 2.0 is unstable You can check the detail information at: http://packages.yoctoproject.org/ Package Version Upstream version Maintainer NoUpgradeReason --- --- -- nfs-utils 1.3.11.3.2 Alejandro Hernandez midori0.5.80.5.9 Alejandro Hernandez python-smmap 0.8.20.9.0 Alejandro Hernandez python3 3.3.33.5.0a3 Alejandro Hernandez python2.7.93.5.0a3 Alejandro Hernandez which 2.20 2.21 Alejandro Hernandez gnome-icon-theme 2.31.0 3.12.0Alejandro Hernandez waiting for the sato gtk3 port jpeg 8d 9aAníbal Limón webkit-gtk 1.8.3 doesn't wo... dpkg 1.17.21 1.17.24 Aníbal Limón sqlite3 3.8.7.4 3.8.8.3. Aníbal Limón mc4.8.13 4.8.14Aníbal Limón screen4.0.34.2.1 Aníbal Limón nettle2.7.13.1rc1Armin Kuster 3.0.0 breaks gnutls, api ch... pinentry 0.9.00.9.1 Armin Kuster linux-libc-headers3.19 3.19.3Bruce Ashfield busybox 1.23.1 1.23.2Chen Qi console-tools 0.3.21999.03.02Chen Qi util-linux2.25.2 2.26.1Chen Qi kmod 19+gitX 20+gitAUTOINC+a8c... Chen Qi curl 7.40.0 7.41.0Chen Qi sudo 1.8.11p2 1.8.13Chen Qi sysstat 11.0.2 11.1.3Chen Qi xz5.2.05.2.1 Chen Qi dbus-glib 0.1020.104 Chong Lu dbus-test 1.8.10 1.9.14Chong Lu dbus 1.8.10 1.9.14Chong Lu D-BUS 1.9.x is the developm... bison 2.7.13.0.4 Chong Lu strace4.9 4.10 Chong Lu tcl 8.6.38.6.4 Chong Lu libuser 0.60 0.61 Chong Lu bluez44.1015.29 Cristian Iorga BlueZ 5.x is not backward-c... gst-plugin-bluetooth 4.1015.29 Cristian Iorga bluez55.28 5.29 Cristian Iorga iproute2 3.17.0 3.19.0Cristian Iorga libpcap 1.6.21.7.2 Cristian Iorga wpa-supplicant2.3 2.4 Cristian Iorga alsa-lib 1.0.28 1.0.29Cristian Iorga alsa-utils-alsaconf 1.0.28 1.0.29Cristian Iorga alsa-utils1.0.28 1.0.29Cristian Iorga gst-ffmpeg0.10.13 0.11.2Cristian Iorga gst-fluendo-mp3 0.10.31 0.10.32 Cristian Iorga gst-plugins-bad 0.10.23 1.4.5 Cristian Iorga not compatible with gst-flu... gst-plugins-base 0.10.36 1.4.5 Cristian Iorga not compatible with gst-flu... gst-plugins-good 0.10.31 1.4.5 Cristian Iorga not compatible with gst-flu... gst-plugins-ugly 0.10.19 1.4.5 Cristian Iorga gstreamer 0.10.36 1.4.5 Cristian Iorga not compatible with gst-fl... libvorbis 1.3.41.3.5 Cristian Iorga libatomics-ops7.2 7.4.0 Cristian Iorga speex 1.2rc1 1.2rc2Cristian Iorga qemu 2.2.02.2.1 Cristian Iorga db6.0.30 6.1.23.NC Cristian Iorga API compatibility issue libical 1.0.01.0.1 Cristian Iorga quota 4.01 4.02 Cristian Iorga harfbuzz 0.9.38 0.9.40Cristian Iorga hwlatdetect 0.89 0.91 Darren Hart rt-tests 0.89 0.91
Re: [yocto] [PATCH] nightly-weston.conf: Run regular build tests for no-X11 case
On 28 March 2015 at 15:33, Paul Eggleton paul.eggle...@linux.intel.com wrote: When I wrote the bug I was thinking more of systems with no graphics at all rather than with Weston replacing X11 - not that we shouldn't be testing Weston though I guess. I guess there's value in both. I for one certainly want to see the non-X11 but still GL-enabled codepaths exerised for the Mesa/GTK+/GStreamer stacks. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] nightly-weston.conf: Run regular build tests for no-X11 case
On 28 March 2015 at 01:33, Graydon, Tracy tracy.gray...@intel.com wrote: +'atextappend' : '\nDISTRO_FEATURES_remove = x11\n'}}, FYI, _remove doesn't encourage leading whitespace. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] nightly-weston.conf: Run regular build tests for no-X11 case
On 28 March 2015 at 15:33, Paul Eggleton paul.eggle...@linux.intel.com wrote:
Hi Tracy,
On Friday 27 March 2015 18:33:08 Graydon, Tracy wrote:
[YOCTO #6854]
A common configuration selection is to remove x11 from
DISTRO_FEATURES. Add a nightly-weston.conf builset to allow us to test this
via the autobuilder. Also added to nightly.conf and yoctoAB.conf.
Signed-off-by: Graydon, Tracy tracy.gray...@intel.com
---
buildset-config.controller/nightly-weston.conf | 24
buildset-config.controller/nightly.conf|
2 +-
buildset-config.controller/yoctoAB.conf| 5 +++--
3 files changed, 28 insertions(+), 3 deletions(-)
create mode 100644 buildset-config.controller/nightly-weston.conf
diff --git a/buildset-config.controller/nightly-weston.conf
b/buildset-config.controller/nightly-weston.conf new file mode 100644
index 000..d9875c6
--- /dev/null
+++ b/buildset-config.controller/nightly-weston.conf
@@ -0,0 +1,24 @@
+[nightly-weston]
+builders: 'example-worker'
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
+ 'branch':'master'}},
+{'meta-qt3':
+{'repourl':'git://git.yoctoproject.org/meta-qt3',
+ 'branch':'master'}}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'i686',
+'distro': 'poky', 'buildhistory' : False}}, +
'atextappend' : '\nDISTRO_FEATURES_remove =
x11\n'}}, +{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
+{'SyncPersistDB' : {'distro' : 'poky'}},
+{'GetBitbakeVersion': {}},
+{'BuildImages': {'images': 'core-image-weston'}},
+{'PublishLayerTarballs':{}},
+{'SendErrorReport': {}},
+{'UploadToasterEventlog': {}},
+{'PublishArtifacts': {'artifacts': ['qemux86-64', 'md5sums']}}]
diff --git a/buildset-config.controller/nightly.conf
b/buildset-config.controller/nightly.conf index cf7c77c..13235bf 100644
--- a/buildset-config.controller/nightly.conf
+++ b/buildset-config.controller/nightly.conf
@@ -88,7 +88,7 @@ steps: [{'SetDest':{}},
'eclipse-plugin-kepler': {},
'eclipse-plugin-juno': {}, 'nightly-non-gpl3': {}, 'nightly-oecore': {},
'nightly-world':{}, 'nightly-world-lsb':{}, 'nightly-intel-gpl': {}, -
'poky-tiny': {}, 'buildtools': {},
+ 'nightly-weston':{}, 'poky-tiny': {},
'buildtools': {}, 'nightly-qa-systemd': {}, 'nightly-qa-extras': {},
'nightly-qa-logrotate': {}, 'nightly-qa-pam': {}, 'nightly-qa-skeleton':
{,
diff --git a/buildset-config.controller/yoctoAB.conf
b/buildset-config.controller/yoctoAB.conf index 5bc369d..ab771c0 100644
--- a/buildset-config.controller/yoctoAB.conf
+++ b/buildset-config.controller/yoctoAB.conf
@@ -6,5 +6,6 @@ order: ['nightly', 'eclipse-plugin-juno',
'nightly-x86-64', 'nightly-x86-64-lsb', 'nightly-x86',
'nightly-x86-lsb', 'nightly-x32', 'nightly-multilib',
'nightly-world', 'nightly-world-lsb', 'nightly-non-gpl3',
-'nightly-oecore', 'nightly-intel-gpl', 'poky-tiny',
-'build-appliance', 'nightly-qa-extras', 'nightly-qa-systemd']
+'nightly-oecore', 'nightly-intel-gpl', 'nightly-weston',
+'poky-tiny', 'build-appliance',
+'nightly-qa-extras', 'nightly-qa-systemd']
When I wrote the bug I was thinking more of systems with no graphics
at all rather than with Weston replacing X11 - not that we shouldn't be
testing Weston though I guess.
Suggestion on which image to replace it with? I agree, there is value
in both. nightly-noX11, I'd imagine.
-b
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Elizabeth Flanagan
Yocto Project
Build and Release
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] nightly-arch*.conf: Add GetBitbakeVersion build step
Pulled to master. Production post-1.8
On 28 March 2015 at 00:36, Graydon, Tracy tracy.gray...@intel.com wrote:
[YOCTO #7519]
Add the GetBitbakeVersion build step to nightly-arch*.conf buildsets
in buildset_config.controller to enable toaster on autobuilder.
Signed-off-by: Graydon, Tracy tracy.gray...@intel.com
---
buildset-config.controller/nightly-arm-lsb.conf | 1 +
buildset-config.controller/nightly-arm.conf | 1 +
buildset-config.controller/nightly-arm64.conf | 1 +
buildset-config.controller/nightly-fsl-arm-lsb.conf | 1 +
buildset-config.controller/nightly-fsl-arm.conf | 1 +
buildset-config.controller/nightly-fsl-ppc-lsb.conf | 1 +
buildset-config.controller/nightly-fsl-ppc.conf | 1 +
buildset-config.controller/nightly-mips-lsb.conf| 1 +
buildset-config.controller/nightly-mips.conf| 1 +
buildset-config.controller/nightly-ppc-lsb.conf | 1 +
buildset-config.controller/nightly-ppc.conf | 1 +
buildset-config.controller/nightly-x86-64-lsb.conf | 1 +
buildset-config.controller/nightly-x86-64.conf | 1 +
buildset-config.controller/nightly-x86-lsb.conf | 1 +
buildset-config.controller/nightly-x86.conf | 1 +
15 files changed, 15 insertions(+)
diff --git a/buildset-config.controller/nightly-arm-lsb.conf
b/buildset-config.controller/nightly-arm-lsb.conf
index 261a1e3..f950b6d 100644
--- a/buildset-config.controller/nightly-arm-lsb.conf
+++ b/buildset-config.controller/nightly-arm-lsb.conf
@@ -15,6 +15,7 @@ steps: [{'SetDest':{}},
'distro': 'poky-lsb', 'buildhistory' : True}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
{'SyncPersistDB' : {'distro' : 'poky-lsb'}},
+{'GetBitbakeVersion': {}},
{'BuildImages': {'images': 'core-image-lsb core-image-lsb-dev
core-image-lsb-sdk core-image-lsb-qt3'}},
{'CreateAutoConf': {'machine': 'beagleboard', 'SDKMACHINE' : 'i686',
'distro': 'poky-lsb'}},
{'BuildImages': {'images': 'core-image-lsb core-image-lsb-sdk'}},
diff --git a/buildset-config.controller/nightly-arm.conf
b/buildset-config.controller/nightly-arm.conf
index d705bbc..ae73381 100644
--- a/buildset-config.controller/nightly-arm.conf
+++ b/buildset-config.controller/nightly-arm.conf
@@ -14,6 +14,7 @@ steps: [{'SetDest':{}},
{'CreateAutoConf': {'machine': 'qemuarm', 'SDKMACHINE' : 'i686',
'distro': 'poky', 'buildhistory' : True}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
{'SyncPersistDB' : {'distro' : 'poky'}},
+{'GetBitbakeVersion': {}},
{'BuildImages': {'images': 'core-image-sato core-image-sato-dev
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
{'RunSanityTests': {'images': 'core-image-minimal core-image-sato
core-image-sato-sdk'}},
{'CreateAutoConf': {'machine': 'beagleboard', 'SDKMACHINE' : 'i686',
'distro': 'poky'}},
diff --git a/buildset-config.controller/nightly-arm64.conf
b/buildset-config.controller/nightly-arm64.conf
index 9595b3b..0b15ec8 100644
--- a/buildset-config.controller/nightly-arm64.conf
+++ b/buildset-config.controller/nightly-arm64.conf
@@ -14,6 +14,7 @@ steps: [{'SetDest':{}},
{'CreateAutoConf': {'machine': 'qemuarm64', 'SDKMACHINE' :'i686',
'distro': 'poky', 'buildhistory' : True}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
{'SyncPersistDB' : {'distro' : 'poky'}},
+{'GetBitbakeVersion': {}},
{'BuildImages': {'images': 'core-image-sato core-image-sato-dev
core-image-sato-sdk core-image-minimal core-image-minimal-dev'}},
{'RunSanityTests': {'images': 'core-image-minimal core-image-sato
core-image-sato-sdk'}},
{'CreateAutoConf': {'machine': 'qemuarm64', 'SDKMACHINE' : 'i686',
'distro': 'poky', 'buildhistory' : False}},
diff --git a/buildset-config.controller/nightly-fsl-arm-lsb.conf
b/buildset-config.controller/nightly-fsl-arm-lsb.conf
index cccb7a1..4599247 100644
--- a/buildset-config.controller/nightly-fsl-arm-lsb.conf
+++ b/buildset-config.controller/nightly-fsl-arm-lsb.conf
@@ -19,6 +19,7 @@ steps: [{'SetDest':{}},
'atextprepend': 'ACCEPT_FSL_EULA = 1\n',
'devkernel' : False}},
{'CreateBBLayersConf': {'buildprovider' : 'yocto', 'bsplayer' :
True, 'bspprovider' : 'fsl-arm'}},
+{'GetBitbakeVersion': {}},
{'BuildImages': {'images': 'core-image-lsb core-image-lsb-dev
core-image-lsb-sdk core-image-lsb-qt3'}},
{'CreateAutoConf': {'machine': 'imx6qsabresd', 'SDKMACHINE' :
'x86_64',
'distro': 'poky-lsb', 'buildhistory' : False,
diff --git a/buildset-config.controller/nightly-fsl-arm.conf
b/buildset-config.controller/nightly-fsl-arm.conf
index a133f3c..e5ca381 100644
--- a/buildset-config.controller/nightly-fsl-arm.conf
+++
[yocto] [meta-raspberrypi][PATCH] spitools : Add new package
Signed-off-by: texierp ouf_du...@hotmail.com --- recipes-devtools/spitools/spitools_git.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/recipes-devtools/spitools/spitools_git.bb b/recipes-devtools/spitools/spitools_git.bb index 287e3eb..128ad7f 100644 --- a/recipes-devtools/spitools/spitools_git.bb +++ b/recipes-devtools/spitools/spitools_git.bb @@ -1,5 +1,6 @@ DESCRIPTION = This package contains some simple command line tools to help using Linux spidev devices HOMEPAGE = https://github.com/cpb-/spi-tools; +AUTHOR = Christophe BLAESS LICENSE=GPLv2 LIC_FILES_CHKSUM = file://LICENSE;md5=8c1ae6c159876a0ba63099614381 -- 1.9.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-raspberrypi][PATCH] This patch add a powerful tool : spitools
---
recipes-devtools/spitools/spitools_git.bb | 15 +++
1 file changed, 15 insertions(+)
create mode 100644 recipes-devtools/spitools/spitools_git.bb
diff --git a/recipes-devtools/spitools/spitools_git.bb
b/recipes-devtools/spitools/spitools_git.bb
new file mode 100644
index 000..287e3eb
--- /dev/null
+++ b/recipes-devtools/spitools/spitools_git.bb
@@ -0,0 +1,15 @@
+DESCRIPTION = This package contains some simple command line tools to help
using Linux spidev devices
+HOMEPAGE = https://github.com/cpb-/spi-tools;
+LICENSE=GPLv2
+LIC_FILES_CHKSUM = file://LICENSE;md5=8c1ae6c159876a0ba63099614381
+
+S = ${WORKDIR}/git
+
+SRC_URI = git://github.com/cpb-/spi-tools.git;protocol=git
+
+SRCREV = cc6a41fdcec60610703ba6db488c621c64952898
+
+COMPATIBLE_MACHINE = raspberrypi
+
+inherit autotools
+
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] spitools : Add new package
On 2015-03-30 00:20, texierp wrote: Signed-off-by: texierp ouf_du...@hotmail.com --- recipes-devtools/spitools/spitools_git.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/recipes-devtools/spitools/spitools_git.bb b/recipes-devtools/spitools/spitools_git.bb index 287e3eb..128ad7f 100644 --- a/recipes-devtools/spitools/spitools_git.bb +++ b/recipes-devtools/spitools/spitools_git.bb @@ -1,5 +1,6 @@ DESCRIPTION = This package contains some simple command line tools to help using Linux spidev devices HOMEPAGE = https://github.com/cpb-/spi-tools; +AUTHOR = Christophe BLAESS LICENSE=GPLv2 LIC_FILES_CHKSUM = file://LICENSE;md5=8c1ae6c159876a0ba63099614381 The email subject line doesn't match what's happening in the patch. Also, why put this in meta-raspberrypi? It probably makes more sense to put it in meta-oe since it doesn't seem to be RaspberryPi specific. -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [linux-yocto] multiple compilers
Hi, There are two solutions, you can specify a preferred compiler in a recipe or change the main compiler. To change preferred compiler in a recipe: TOOLCHAIN_pn-recipe-name = your_compiler DEPENDS_append_pn-recipe-name = your_compiler-cross To change the main compiler: TOOLCHAIN = your_compiler There is a example in the official wiki : http://www.openembedded.org/wiki/Adding_a_secondary_toolchain Best regards, Thomas P. On Fri, Mar 27, 2015 at 10:32 PM, Mehaffey, John john_mehaf...@mentor.com wrote: Hi Dan, I don't generally do compilers, but the Yocto way is to create another recipe where the SRC_URI points to the tarball/git repository you want to build from. It may be that you will need to start with an older compiler .bb recipe, you don't say how far back you need to go. You don't really say what you've tried, so I can't help much with specifics, as I am not sure of your level of proficiency with Yocto/bitbake. Sincerely, John Mehaffey Linux System Architect Mentor Graphics From: linux-yocto-boun...@yoctoproject.org [linux-yocto-boun...@yoctoproject.org] on behalf of Dan Gundlach [cyclist2...@gmail.com] Sent: Friday, March 27, 2015 1:33 PM To: linux-yocto@yoctoproject.org Subject: [linux-yocto] multiple compilers How do I configure yocto to create multiple compilers? I need to create a second (older) compiler to build the kernel. It won't boot using the current one. I've searched in vain to find a solution. It says you can do it, but it dosn't tell you how. -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[yocto] Yocto menuconfig not working
For some reason the menuconfig menu does not come up when I try launching it from my Yocto installation. I am using the Toradex Yocto 1.6 system as is described here http://developer.toradex.com/software-resources/arm-family/linux/board-support-package/openembedded-%28core%29, with my board set to apalis-t30. When I run either bitbake virtual/kernal -c menuconfig or bitbake linux-toradex -c menuconfig, it executes fine but finishes (without erros) before actually showing anything. Running devshell also gives the same results. If I just use the kernel sources on their own as is described here http://developer.toradex.com/software-resources/arm-family/linux/board-support-package/build-u-boot-and-linux-kernel-from-source-code, I can get menuconfig open using make nconfig. From the Yocto scripts it appears as if though the exact same kernel sources are being used. If I try adding adding make nconfig to the do_configure_prepend script in the linux-toradex_git.bb file then the commands get stuck stating that the process (I assume menuconfig) is running and then provides a PID for it, but no window or menu is displayed anywhere and the task does not seem to finish. PS. I am on Fedora 21 64-bit. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[linux-yocto] [PATCH] LSI AXXIA updates to 3.4 standard/axxia/base
From: Cristian Bercaru cristian.berc...@windriver.com Hello! This patch is an update to IBM PPC476 erratum 48 fix and it is tagged with the latest 3.4 tag: lsi_axxia_linux_7.8.1.43. Sangeetha Rao (1): arch/powerpc/kernel: Address IBM PPC476 erratum 48 (update) arch/powerpc/kernel/traps.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) -- 1.7.9.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[yocto] yocto master work-shared, kernel .config seems to have gone awol
Hi, I'm updating to Yocto master and have been seeing that when I bitbake -c devshell virtual/kernel I go into a work-shared tree now. (This is all with meta-fsl-arm) I'd normally change the kernel configuration with bitbake -c menuconfig virtual/kernel then pull out the .config and make my changes to defconfig as needed. But I can't seem to find it any more, either in work-shared or if I traverse to the work tree. No doubt my own stupidity here but where is it supposed to be nowadays? Could anybody point me to a discussion on how things are going to be broken out into work-shared and (presumably) work so I can get up to speed? Not finding the configuration I thought I'd try generating a kernel fragment with bitbake -c diffconfig virtual/kernel from the Yocto docs but I can't see a fragment.cfg anywhere in the tree I guess this could all be just that meta-fsl-arm isn't quick in sync with current the current master? (assuming it's not the more likely explanation that I just have this plain wrong) Thanks, Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[linux-yocto] [PATCH] LSI AXXIA updates to 3.4 standard/axxia/base
From: Cristian Bercaru cristian.berc...@windriver.com Hello! This patch is an update to IBM PPC476 erratum 48 fix and it is tagged with the latest 3.4 tag: lsi_axxia_linux_7.8.1.43. Sangeetha Rao (1): arch/powerpc/kernel: Address IBM PPC476 erratum 48 (update) arch/powerpc/kernel/traps.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) -- 1.7.9.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[yocto] [RFC] Toaster integration with Jenkins
We are considering working on integrating Toaster with Jenkins as part of the next Yocto Project release. Our thinking so far is collected in this Bugzilla feature: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7527 Any thoughts? Are we missing something? Are we going about it in a completely wrong way? Let us know. Thanks! Belén -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [autobuilder 1/1] UploadToasterEventlog: fix bitbake eventlog file path
From: Alexandru Damian alexandru.dam...@intel.com The UploadToasterEventlog looks the file up in the wrong directory, and this patch fixes that. Signed-off-by: Alexandru DAMIAN alexandru.dam...@intel.com --- .../site-packages/autobuilder/buildsteps/UploadToasterEventlog.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/python2.7/site-packages/autobuilder/buildsteps/UploadToasterEventlog.py b/lib/python2.7/site-packages/autobuilder/buildsteps/UploadToasterEventlog.py index a1e480f..81d8ed8 100644 --- a/lib/python2.7/site-packages/autobuilder/buildsteps/UploadToasterEventlog.py +++ b/lib/python2.7/site-packages/autobuilder/buildsteps/UploadToasterEventlog.py @@ -36,7 +36,7 @@ class UploadToasterEventlog(ShellCommand): self.layerversion_core = self.getProperty(layerversion_core) self.filepath=os.path.join(os.path.join( self.workerdir, self.buildername), -build/bitbake_eventlog.json) +build/build/bitbake_eventlog.json) if int(self.layerversion_core) 4: self.command = echo 'Skipping Step.' -- 1.9.1 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[linux-yocto] [PATCH] arch/powerpc/kernel: Address IBM PPC476 erratum 48 (update)
From: Sangeetha Rao sangeetha@intel.com
This patch updates the fix to PPC476 erratum 48 in order to use the
correct calculation for L2 cache register for CPUs 4 and 5.
Signed-off-by: Sangeetha Rao sangeetha@intel.com
---
arch/powerpc/kernel/traps.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/kernel/traps.c b/arch/powerpc/kernel/traps.c
index b4b4048..cc036fb 100644
--- a/arch/powerpc/kernel/traps.c
+++ b/arch/powerpc/kernel/traps.c
@@ -866,8 +866,8 @@ void machine_check_exception(struct pt_regs *regs)
mtdcr((cpu + 3) * 256, 0x304);
l2plbstats1 = mfdcr((cpu + 3) * 256 + 4);
} else {
- mtdcr((cpu + 9)*256, 0x304);
- l2plbstats1 = mfdcr((cpu + 9) * 256 + 4);
+ mtdcr((cpu + 15) * 256, 0x304);
+ l2plbstats1 = mfdcr((cpu + 15) * 256 + 4);
}
if (((mcsr 0x8020) == 0x8020)
@@ -879,7 +879,7 @@ void machine_check_exception(struct pt_regs *regs)
mtdcr((cpu + 3) * 256 + 4,
0x000C);
} else {
- mtdcr((cpu + 9) * 256 + 4,
+ mtdcr((cpu + 15) * 256 + 4,
0x000C);
}
printk(KERN_INFO machine_check_exception: Core %d: MCSR=0x%x
l2plbstats1=0x%x,
--
1.7.9.5
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] LSI AXXIA updates to 3.4 standard/axxia/base
On 2015-03-30 01:10 PM, cristian.berc...@windriver.com wrote: From: Cristian Bercaru cristian.berc...@windriver.com Hello! This patch is an update to IBM PPC476 erratum 48 fix and it is tagged with the latest 3.4 tag: lsi_axxia_linux_7.8.1.43. This came through multiple times .. is this the right version ? This patch won't apply to the linux-yocto-3.4 standard/axxxia/base branch: yow-bashfiel-d4 [/home/brucgit-merge] git am -s a.mbox Applying: arch/powerpc/kernel: Address IBM PPC476 erratum 47 error: patch failed: arch/powerpc/kernel/head_44x.S:1249 error: arch/powerpc/kernel/head_44x.S: patch does not apply Patch failed at 0001 arch/powerpc/kernel: Address IBM PPC476 erratum 47 The copy of the patch that failed is found in: /home/bruce/poky-kernel/linux-yocto-3.4.git-merge/.git/rebase-apply/patch When you have resolved this problem, run git am --continue. If you prefer to skip this patch, run git am --skip instead. To restore the original branch and stop patching, run git am --abort. Bruce Sangeetha Rao (1): arch/powerpc/kernel: Address IBM PPC476 erratum 48 (update) arch/powerpc/kernel/traps.c |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [yocto] [RFC] Toaster integration with Jenkins
On Mon, Mar 30, 2015 at 11:47 AM, Barros Pena, Belen belen.barros.p...@intel.com wrote: We are considering working on integrating Toaster with Jenkins as part of the next Yocto Project release. Our thinking so far is collected in this Bugzilla feature: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7527 Any thoughts? Are we missing something? Are we going about it in a completely wrong way? I think is a great idea and will be really useful for some current infrastructures Best regards Victor Rodriguez Let us know. Thanks! Belén -- ___ 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] yocto master work-shared, kernel .config seems to have gone awol
On 30 March 2015 at 18:36, Alex J Lennon ajlen...@dynamicdevices.co.uk
wrote:
I'm updating to Yocto master and have been seeing that when I bitbake -c
devshell virtual/kernel I go into a work-shared tree now.
The devshell drops you into whatever ${S} is for that recipe, which for the
kernel is ${STAGING_KERNEL_DIR} since the kernel optimisations. For the
kernel yes, this is sub-optimal. Maybe the kernel should override this
using the variable I added (as Bruce mentioned).
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto master work-shared, kernel .config seems to have gone awol
On 2015-03-30 01:36 PM, Alex J Lennon wrote: Hi, I'm updating to Yocto master and have been seeing that when I bitbake -c devshell virtual/kernel I go into a work-shared tree now. There was a discussion on the list about this. See the patch from Ross: [OE-core] [PATCH] devshell: allow the starting directory to be overridden Since there are those that want to be in the source dir, and those that want to be in the build dir .. there's a variable to make that change. (This is all with meta-fsl-arm) I'd normally change the kernel configuration with bitbake -c menuconfig virtual/kernel then pull out the .config and make my changes to defconfig as needed. In this case, you need to be in the source tree, but have your output pointing to the build dir. That used to be set when you dropped into the devshell, check and see if KBUILD_OUTPUT is set. But I can't seem to find it any more, either in work-shared or if I traverse to the work tree. No doubt my own stupidity here but where is it supposed to be nowadays? Could anybody point me to a discussion on how things are going to be broken out into work-shared and (presumably) work so I can get up to speed? Most of the changes are documented in the commits that make the switch, and you'll see them proposed on the oe-core mailing list by Richard, with me following up with comments and details. Bruce Not finding the configuration I thought I'd try generating a kernel fragment with bitbake -c diffconfig virtual/kernel from the Yocto docs but I can't see a fragment.cfg anywhere in the tree I guess this could all be just that meta-fsl-arm isn't quick in sync with current the current master? (assuming it's not the more likely explanation that I just have this plain wrong) Thanks, Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] Gracefully abort if rootfs.img gets to big
Hi Armin,
Great catching up with you last week, and thanks for looking at my
patch. I supposed it's a double edged sword. If we make it a
variable, it can be set wrong and the build hang again. OTOH, 128MB
is probably way more space than we really need to reserve, and I
supposed if someone were just banging up against the limit, they might
want to tweak it. I'll defer to the collective judgement of the
group, and resubmit if that's the consensus.
Oh, and silly me...I figured the mail list daemon would put the
[Yocto] tag on the patch. Since it seems to tag our posts, that is a
mystery to me. Maybe Michael can enlighten me off list. :-P
-Chris
On Mon, Mar 30, 2015 at 6:51 PM, akuster808 akuster...@gmail.com wrote:
Chris,
Should the hardcoded value '416080' be a variable so it can be
overridden?
- armin
On 03/30/2015 01:50 PM, Chris Hallinan wrote:
See https://bugzilla.yoctoproject.org/show_bug.cgi?id=7541
Current implementation of live image type cannot support image size
greater than 4GB. If the image gets too large, the build simply
hangs silently, without any clues or debug output to indicate why.
This patch prevents the build hanging on rootfs.img getting too big.
---
meta/classes/bootimg.bbclass | 7 +++
1 file changed, 7 insertions(+)
diff --git a/meta/classes/bootimg.bbclass b/meta/classes/bootimg.bbclass
index b1c03ba..e143e24 100644
--- a/meta/classes/bootimg.bbclass
+++ b/meta/classes/bootimg.bbclass
@@ -84,6 +84,13 @@ populate() {
fi
if [ -n ${ROOTFS} ] [ -s ${ROOTFS} ]; then
+ ROOTFS_FILE_SIZE=`stat -L -c %s ${ROOTFS}`
+ bbnote do_bootimg(): rootfs.img size =
${ROOTFS_FILE_SIZE}
+ # Actual limit is difficult to determine
+ # This leaves ~128MiB headroom for initrd and boot files
+ if [ ${ROOTFS_FILE_SIZE} -gt 416080 ]; then
+ bbfatal Root fs (rootfs.img) is too big for live
image
+ fi
install -m 0644 ${ROOTFS} ${DEST}/rootfs.img
fi
--
Life is like Linux - it never stands still.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] Gracefully abort if rootfs.img gets to big
See https://bugzilla.yoctoproject.org/show_bug.cgi?id=7541
Current implementation of live image type cannot support image size
greater than 4GB. If the image gets too large, the build simply
hangs silently, without any clues or debug output to indicate why.
This patch prevents the build hanging on rootfs.img getting too big.
---
meta/classes/bootimg.bbclass | 7 +++
1 file changed, 7 insertions(+)
diff --git a/meta/classes/bootimg.bbclass b/meta/classes/bootimg.bbclass
index b1c03ba..e143e24 100644
--- a/meta/classes/bootimg.bbclass
+++ b/meta/classes/bootimg.bbclass
@@ -84,6 +84,13 @@ populate() {
fi
if [ -n ${ROOTFS} ] [ -s ${ROOTFS} ]; then
+ ROOTFS_FILE_SIZE=`stat -L -c %s ${ROOTFS}`
+ bbnote do_bootimg(): rootfs.img size = ${ROOTFS_FILE_SIZE}
+ # Actual limit is difficult to determine
+ # This leaves ~128MiB headroom for initrd and boot files
+ if [ ${ROOTFS_FILE_SIZE} -gt 416080 ]; then
+ bbfatal Root fs (rootfs.img) is too big for live image
+ fi
install -m 0644 ${ROOTFS} ${DEST}/rootfs.img
fi
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH] Gracefully abort if rootfs.img gets to big
Chris,
Should the hardcoded value '416080' be a variable so it can be
overridden?
- armin
On 03/30/2015 01:50 PM, Chris Hallinan wrote:
See https://bugzilla.yoctoproject.org/show_bug.cgi?id=7541
Current implementation of live image type cannot support image size
greater than 4GB. If the image gets too large, the build simply
hangs silently, without any clues or debug output to indicate why.
This patch prevents the build hanging on rootfs.img getting too big.
---
meta/classes/bootimg.bbclass | 7 +++
1 file changed, 7 insertions(+)
diff --git a/meta/classes/bootimg.bbclass b/meta/classes/bootimg.bbclass
index b1c03ba..e143e24 100644
--- a/meta/classes/bootimg.bbclass
+++ b/meta/classes/bootimg.bbclass
@@ -84,6 +84,13 @@ populate() {
fi
if [ -n ${ROOTFS} ] [ -s ${ROOTFS} ]; then
+ ROOTFS_FILE_SIZE=`stat -L -c %s ${ROOTFS}`
+ bbnote do_bootimg(): rootfs.img size = ${ROOTFS_FILE_SIZE}
+ # Actual limit is difficult to determine
+ # This leaves ~128MiB headroom for initrd and boot files
+ if [ ${ROOTFS_FILE_SIZE} -gt 416080 ]; then
+ bbfatal Root fs (rootfs.img) is too big for live image
+ fi
install -m 0644 ${ROOTFS} ${DEST}/rootfs.img
fi
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] distro_alias.inc: update/sort alias information.
Added new package data, and cleaned up whitespace. I've also corrected some packaged data (replacement-tar from my reading of the recipe is the tar normally found in distros). One issue this patch exposed st I haven't had a chance to track down is that when you attempt to get distrodata from gcc-crosssdk-initial-x86_64. The produced .csv in tmp/log is missing the Distro information. bitbake -e shows that DISTRO_PN_ALIAS isn't even getting set in this case. My guess here is that something is happening with the _ along the way, I've just not found it yet. Signed-off-by: Beth Flanagan elizabeth.flana...@intel.com --- meta-yocto/conf/distro/include/distro_alias.inc | 41 + 1 file changed, 35 insertions(+), 6 deletions(-) diff --git a/meta-yocto/conf/distro/include/distro_alias.inc b/meta-yocto/conf/distro/include/distro_alias.inc index 48c1d92..2c35c28 100644 --- a/meta-yocto/conf/distro/include/distro_alias.inc +++ b/meta-yocto/conf/distro/include/distro_alias.inc @@ -1,6 +1,6 @@ # # This is a list for tracking status of package relative to Major -# distributions such as Fedora, Ubuntu, Debian, ... The package +# distributions such as Fedora, Ubuntu, Debian, ... The package # name is the major distribution equivalent to the name used in oe-core # # The format is as a bitbake variable override for each recipe @@ -54,6 +54,7 @@ DISTRO_PN_ALIAS_pn-core-image-base = OE-Core DISTRO_PN_ALIAS_pn-core-image-clutter = OE-Core DISTRO_PN_ALIAS_pn-core-image-directfb = OE-Core DISTRO_PN_ALIAS_pn-core-image-full-cmdline = OE-Core +DISTRO_PN_ALIAS_pn-core-image-kernel-dev = OE-Core DISTRO_PN_ALIAS_pn-core-image-lsb = OE-Core DISTRO_PN_ALIAS_pn-core-image-lsb-dev = OE-Core DISTRO_PN_ALIAS_pn-core-image-lsb-qt3 = OE-Core @@ -67,14 +68,19 @@ DISTRO_PN_ALIAS_pn-core-image-rt-sdk = OE-Core DISTRO_PN_ALIAS_pn-core-image-sato = OE-Core DISTRO_PN_ALIAS_pn-core-image-sato-dev = OE-Core DISTRO_PN_ALIAS_pn-core-image-sato-sdk = OE-Core +DISTRO_PN_ALIAS_pn-core-image-testmaster = OE-Core +DISTRO_PN_ALIAS_pn-core-image-testmaster-initramfs = OE-Core DISTRO_PN_ALIAS_pn-core-image-weston = OE-Core DISTRO_PN_ALIAS_pn-core-image-x11 = OE-Core DISTRO_PN_ALIAS_pn-cross-localedef = OSPDT DISTRO_PN_ALIAS_pn-cryptodev-linux = OE-Core +DISTRO_PN_ALIAS_pn-cryptodev-module = OE-Core +DISTRO_PN_ALIAS_pn-cryptodev-tests = OE-Core DISTRO_PN_ALIAS_pn-cwautomacros = OSPDT upstream=http://cwautomacros.berlios.de/; DISTRO_PN_ALIAS_pn-damageproto = Meego=xorg-x11-proto-damageproto DISTRO_PN_ALIAS_pn-db = Debian=db5.1 Ubuntu=db5.1 DISTRO_PN_ALIAS_pn-dbus-ptest = Fedora=dbus Ubuntu=dbus +DISTRO_PN_ALIAS_pn-dbus-test = Fedora=dbus Ubuntu=dbus DISTRO_PN_ALIAS_pn-dbus-wait = OpenedHand DISTRO_PN_ALIAS_pn-depmodwrapper-cross = OE-Core DISTRO_PN_ALIAS_pn-directfb-examples = Debian=directfb Fedora=directfb @@ -85,6 +91,8 @@ DISTRO_PN_ALIAS_pn-docbook-dsssl-stylesheets = Fedora=docbook-style-dsssl Ubunt DISTRO_PN_ALIAS_pn-docbook-sgml-dtd-3.1 = Fedora=docbook-dtds Mandriva=docbook-dtd31-sgml DISTRO_PN_ALIAS_pn-docbook-sgml-dtd-4.1 = Fedora=docbook-dtds Mandriva=docbook-dtd41-sgml DISTRO_PN_ALIAS_pn-docbook-sgml-dtd-4.5 = Fedora=docbook-dtds Mandriva=docbook-dtd42-sgml +DISTRO_PN_ALIAS_pn-docbook-xml-dtd4 = Ubuntu=docbook-xml Fedora=docbook-dtds +DISTRO_PN_ALIAS_pn-docbook-xml-dtd4-native = Ubuntu=docbook-xml Fedora=docbook-dtds DISTRO_PN_ALIAS_pn-dri2proto = Meego=xorg-x11-proto-dri2proto DISTRO_PN_ALIAS_pn-dropbear = Debian=dropbear Ubuntu=dropbear DISTRO_PN_ALIAS_pn-dtc = Fedora=dtc Ubuntu=dtc @@ -112,14 +120,21 @@ DISTRO_PN_ALIAS_pn-gail = Fedora=gail Ubuntu=libgail-3-0 DISTRO_PN_ALIAS_pn-gaku = OpenedHand DISTRO_PN_ALIAS_pn-galago-daemon = Debian=galago-daemon Ubuntu=galago-daemon DISTRO_PN_ALIAS_pn-gcc-cross-initial = OE-Core +DISTRO_PN_ALIAS_pn-gcc-cross-initial-i586 = OE-Core DISTRO_PN_ALIAS_pn-gcc-crosssdk-initial = OE-Core +DISTRO_PN_ALIAS_pn-gcc-crosssdk-initial-x86_64 = OE-Core DISTRO_PN_ALIAS_pn-gccmakedep = Mandriva=gccmakedep Ubuntu=xutils-dev DISTRO_PN_ALIAS_pn-gcc-runtime = Ubuntu=gcc Fedora=gcc +DISTRO_PN_ALIAS_pn-gcc-sanitizers = Ubuntu=gcc Fedora=gcc +DISTRO_PN_ALIAS_pn-gcc-source = Ubuntu=gcc Fedora=gcc DISTRO_PN_ALIAS_pn-gconf-dbus = Meego=GConf-dbus DISTRO_PN_ALIAS_pn-gdk-pixbuf = Debian=libgdk-pixbuf2.0 Fedora=gdk-pixbuf DISTRO_PN_ALIAS_pn-gdk-pixbuf-csource = Debian=libgdk-pixbuf2.0-0 Fedora=gdk-pixbuf2 DISTRO_PN_ALIAS_pn-gettext-minimal = Debian=gettext Fedora=gettext DISTRO_PN_ALIAS_pn-glib-2.0 = Meego=glib2 Fedora=glib2 OpenSuSE=glib2 Ubuntu=glib2.0 Mandriva=glib2.0 Debian=glib2.0 +DISTRO_PN_ALIAS_pn-glibc-locale = OpenSuSE=glibc-locale Fedora=glibc-devel +DISTRO_PN_ALIAS_pn-glibc-mtrace = Fedora=glibc-utils Ubuntu=libc-dev-bin +DISTRO_PN_ALIAS_pn-glibc-scripts = Fedora=glibc Ubuntu=libc-bin DISTRO_PN_ALIAS_pn-glproto = Meego=xorg-x11-proto-glproto DISTRO_PN_ALIAS_pn-gnome-desktop-testing = Debian=gnome-desktop-testing Fedora=gnome-desktop-testing
