linux/poky.git/scripts, branch 1.5_M3.rc1

test-dependencies: add simple script to detect missing or autoenabled dependencies

2013-07-29T12:09:05+00:00

(From OE-Core rev: a2b3c9e01c871a395a93e162731db77a618306cb) Signed-off-by: Martin Jansa Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

scripts/create-lsb-image: remove

2013-07-29T12:09:05+00:00

This script is no longer maintained. Now we don't perform LSB test on qemu image, so we don't need this script. Most of functions in this script are implemented in LSB_Test.sh. So it is safe to remove. (From OE-Core rev: 46a71cdd3a6e8f571610d73b8811c060d038e8bf) Signed-off-by: Yi Zhao Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

scripts/contrib/*: fix arithmetic bashism

2013-07-18T20:25:35+00:00

Apparently $[...] isn't valid in dash, so use $((...)) instead for mkefidisk.sh and ddimage that both start with $!/bin/sh. (From OE-Core rev: d509739ca54e6b70f2dcc216b831fc02c64293a6) Signed-off-by: Paul Eggleton Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

yocto-kernel: make BBLAYERS parsing more robust

2013-07-13T17:23:39+00:00

This allows the BBLAYERS parsing code to handle cases where BBLAYERS is spread across multiple assignments or all on a single line, within double or single quotes. Fixes [YOCTO #3746]. (From meta-yocto rev: 4ab26d9e655bab0069ffe9b135557d943cf1f524) Signed-off-by: Tom Zanussi Signed-off-by: Richard Purdie

scripts/runqemu: Add support for 'qemumicroblaze' machine

2013-07-10T08:41:51+00:00

* Add support to boot the 'qemumicroblaze' machine in qemu-system-microblazeel * Use the specific machine model for a MicroBlaze system 'petalogix-ml605' * Use the DTB generated from the kernel build as the DTB for boot * Force use of initrd rootfs (either in ext or cpio formats) (From OE-Core rev: 2c164a5dfc877d180ef58d46c063573621297929) Signed-off-by: Nathan Rossi Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

scripts/runqemu: Add support for 'qemuzynq' machine

2013-07-10T08:41:51+00:00

* Add support to boot the 'qemuzynq' machine in qemu-system-arm * Use the specific machine model for Zynq 'xilinx-zynq-a9' * Use the DTB generated from the kernel build as the DTB for boot * Force use of initrd rootfs (either in ext or cpio formats) (From OE-Core rev: 1e4b1d95e1f47654e928f38cd091ffe272689844) Signed-off-by: Nathan Rossi Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

lib/oeqa/utils/qemurunner.py: class to handle qemu instance

2013-07-09T09:53:45+00:00

Handles qemu instances (launch, kill, restart, serial connection, logging) Launch is blocking until login prompt and returns to the task. A qemu serial connection is used to save the boot log and get the ip from the image. Changed runqemu script not to error out when using custom serial option. (From OE-Core rev: ee7d64dfcc02ba8f568b17d181e0a58d3c810076) Signed-off-by: Radu Moisan Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

yocto-kernel: enforce exact match for BBLAYERS

2013-07-05T14:40:30+00:00

The current code uses .startswith to find BBLAYERS, which causes false positives when other variables such as BBLAYERS_NON_REMOVABLE exist. This forces an exact match instead of a partial match. Fixes [YOCTO #4743]. (From meta-yocto rev: c039def50ca6c02cb1b66fd4bf76664de42c068e) Signed-off-by: Tom Zanussi Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

yocto-bsp: filter out 'layer' from arch list

2013-07-05T14:40:30+00:00

The yocto-layer tool added a new directory alongside the actual architectures and 'common', which is already screened out as not an actual architecture when displaying the architecures. The same needs to be done for 'layer' which isn't actually an architecuture and likewise needs to be screened out. Fixes [YOCTO #4735]. (From meta-yocto rev: 7459485bf75855a40d124915d38284f737a25cc4) Signed-off-by: Tom Zanussi Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

python-multiprocessing: adding runtime dependencies

2013-06-28T10:02:41+00:00

As python-multiprocessing requires python-threading and python-pickle, this commit adds them as runtime dependency. The observed behavior was: When typing 'import multiprocessing' in the python shell on a minimal image with only the python-multiprocessing recipe installed, python reports at first: Python 2.7.3 (default, Jun 27 2013, 08:26:25) [GCC 4.7.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import multiprocessing; Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/multiprocessing/__init__.py", line 65, in from multiprocessing.util import SUBDEBUG, SUBWARNING File "/usr/lib/python2.7/multiprocessing/util.py", line 38, in import threading # we want threading to install it's ImportError: No module named threading After adding python-threading as runtime dependency and rebuilding the image, python reports: Python 2.7.3 (default, Jun 27 2013, 08:26:25) [GCC 4.7.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import multiprocessing; Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/multiprocessing/__init__.py", line 84, in import _multiprocessing ImportError: No module named cPickle (From OE-Core rev: e913412ca0ff01cb654757c8199e8859f15b7cf7) Signed-off-by: Lukas Bulwahn Signed-off-by: Richard Purdie