summaryrefslogtreecommitdiffstats
path: root/scripts
Commit message (Collapse)AuthorAgeFilesLines
* qemuimage-testlib: Fix quoting issueRichard Purdie2013-04-231-1/+1
| | | | | | (From OE-Core rev: f8628a0649a56c5caae45d1320cf970eb83bcc1c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimage-testlib: Use ww option to ps to ensure command output isn't truncatedRichard Purdie2013-04-231-1/+1
| | | | | | (From OE-Core rev: c7a6d7fa5032a16a9e1f8fa5a563802f9d9fe607) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimage-testlib: Increase qemu startup timeoutsRichard Purdie2013-04-231-2/+3
| | | | | | | | | | We are seeing timeouts on the autobuilder where qemu does start but the script doesn't appear to be able to detect it in time. This patch increases the timeouts since there seems little harm in doing so. (From OE-Core rev: 33a5980ac381409413712b9910ee9638b7958189) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* relocate_sdk.py: allow relocate_sdk.py to work with python 2.4.xJason Wessel2013-04-231-13/+13
| | | | | | | | | | | | | | Avoid the chicken / egg problem of an SDK that provides a working python but requires that version of python to extract itself. The RHEL 5.x systems and some other enterprise Linux systems ship with python 2.4.x as the default python. We need to at least be able to extract work executables even if we never use the the host provided python again. (From OE-Core rev: 9a5ed565758a6fcc94bc85ce6205375d2fd282ea) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* relocate_sdk.py: Fix corruption of sdk binariesJason Wessel2013-04-231-2/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | There are two cases of corruption that the relocate_sdk.py was not correctly dealing with. 1) SDK Extras should be left alone Extra external binaries included in an SDK that were linked against the host's version of /usr/lib/ld-so.so should not get a relocation applied. In the case that was discovered these were LSB compliant binaries that already worked on many hosts. 2) If the interp section is too small generate an error In the case of the qemu user code, it was using its own .ld file to link the executables which overrides the default in the nativesdk binutils. This generated host executables which had a interp section that was too small to relocate. Now the relocate_sdk.py will print an error and continue on such that the error can be fixed by a developer without having to do the difficult task of debugging why it is crashing or not loading correctly. (From OE-Core rev: 4142f6f9392fdd919488151170fb088d4113e0f2) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimage-testlib: Capture stderror in the logs as well as stdoutRichard Purdie2013-03-271-2/+2
| | | | | | | | This allows error messages to be captured in the logs which is helpful. (From OE-Core rev: efb89b3fd5a96da70153f24c849d1436d1ba06cb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimagetest: collect and print runqemu outputPaul Eggleton2013-03-271-2/+8
| | | | | | | | | | | If runqemu (or qemu itself) fails we need to know why, so tee out to a log file and print it when we can't find the qemu process or determine its IP address. (From OE-Core rev: 3faa2d5bc993876f1f8b3ad806a0192efaa43e05) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimagetest: fix erroneous ps errors when qemu couldn't be startedPaul Eggleton2013-03-272-2/+2
| | | | | | | | | | | | The helper script was printing an error to stdout when it couldn't find any qemu child processes; output this error to stderr instead and redirect stderr to /dev/null when running from qemuimage-testlib so that QEMUPID is actually blank if there are no qemu instances found. (From OE-Core rev: 21edf5ec12d8307c528f157c8e078dbefe25d1ef) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/qemu-testlib: Add more debugging informationRichard Purdie2013-03-271-10/+21
| | | | | | | | | | | | | This extra information should allow better forensics if the sanity tests fail as they're currently doing occasionaly on the autobuilder for unknown reasons. The patch also tightens up certain checks to remove pointless noise and error output from the logs. (From OE-Core rev: aef04b2247137fffb8c1b1d776091bbee8637ff9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/runqemu-internal: Fix lock racesRichard Purdie2013-03-271-12/+7
| | | | | | | | | | | | | | | | There are two problems here. Firstly the grep command is unanchored so pid 345 will match against 12345 and so on. The second issue is that there are several context switched between attempting the lock and then writing the pid to it. Between the two issues, there were issues appearing on the autobuilder due to these conflicts. This patch replaces the mechanism with flock on fd 8 which should be a safer mechanism to use. (From OE-Core rev: f1a126f2b0f419b2de573e2367d41d8ccc28b346) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: Improve error handling/exit codesRichard Purdie2013-03-272-16/+19
| | | | | | | | | | | | | runqemu-internal is sourced so should be returning with an error code in case of errors. runqemu needs to deal with this. This patch fixes up the various error paths so we're consistent and get a sane exit status for runqemu which helps a lot in its use in the qemu runtime testing on the autobuilder. (From OE-Core rev: 22a54741167dd6cc011a1b98787c82cc992158ed) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimage-testlib: Add extra debugging and sanity checkRichard Purdie2013-03-271-1/+3
| | | | | | | | | | | Check for a zero IP address since its clearly incorrect if that value is found. Also add debugging for cases where we can't find the qemu process. A process listing is handy to help understand what the problem might be. (From OE-Core rev: a822eff2362ac0284b320b2d45cf9dbf9b9dd73c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimage-testlib: Add delay to work around races in qemu startupRichard Purdie2013-03-271-0/+2
| | | | | | | | | | | Qemu changes pid when starting up. On a loaded machine, this can result in the incorrect pid being returned. Since qemu will take a few seconds to boot anyway, we might as well delay a short while and allow things to settle which should fix various race issues being seen on the autobuilder. (From OE-Core rev: 27d00d62281a822efbbc189a3bab1d9b25fba3a7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimage-testlib: Fix IP address handlingRichard Purdie2013-03-271-4/+2
| | | | | | | | | | Remove some pointless code and also fix the return handling for the function since it returns null, not 0 as the comments would suggest. (From OE-Core rev: 827492e3738bf3b6cf2bc1b9e1108bb28abcb146) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/qemutestlib: Add better process debugging and fix process group issueRichard Purdie2013-03-271-5/+20
| | | | | | | | | | | In single testing with a shutdown scenario the processes are cleaned up correctly but the manual cleanup fall back used for a minimal image do not work properly. This patch fixes the kill commands to revert to non-process groups, fixing the hung process issues that were occuring. (From OE-Core rev: 1c7d4fc88a9e7a3cdb41044ce7eedadd38e99952) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu-testlib: Add python helper and simplify shellRichard Purdie2013-03-273-158/+117
| | | | | | | | | | | | | | | | | | The current code has a race since it greps for *any* qemu process running, even if it isn't the one we started. This leads to some sanity tests potentially failing on machines where multiple sets of sanity tests are running. To resovle this and some other ugly code issues, add a python script to accurately walk the process tree and find the qemu process. We can then replace all the shell functions attempting this which happen to work in many cases but not all. Also clean up some of the error handling so its more legible. (From OE-Core rev: a62263761fc77c139d418236cc52b04bed629229) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/bitbake: Remove all instances of paths to a layer's scripts directory.Franklin S. Cooper Jr2013-03-011-1/+1
| | | | | | | | | | | | | | | | | | | * Currently the assumption is made that only oe-core can include a scripts directory. * However, when other layers create a scripts directory the bitbake script freaks out causing a infinite recursive loop until it crashes. * Simply changing the regular expression to remove all instances of scripts path instead of just the first one fixes this problem. [Yocto Bug 3872] (From OE-Core rev: 00d0e1ac741e5fc01a40feb7dcc7ecd3906b5ce4) Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/qemuimage-testlib: Use wide option to ps callsMichael Halstead2013-02-141-5/+5
| | | | | | | | | | | | | | | Forcing ps to display unlimited column width allows the qemu IP address to be discovered during sanity testing when the command line is extremely long. This seems to fix the sanity testing problem on AB05 which was recently updated to OpenSUSE 12.2. I'm not sure what about qemu or process listing is different on that distribution but this simpile fix seems to work and my help on other distro's as well. (From OE-Core rev: 4d2164494fba2c4c3016fe196f986161a71f70cb) Signed-off-by: Michael Halstead <michael@yoctoproject.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* relocate_sdk.py: new interpreter string was not '\0' terminatedLaurentiu Palcu2013-02-141-2/+2
| | | | | | | | | | | | | | | The problem: SDK binaries were not properly relocated when the SDK was installed into a path that had a length less than the default one. Apparently, there were two problems here: the padding was done wrong (the size of one program header table entry was used instead of the program section size) and the new padded string was not used at all. [YOCTO #3655] (From OE-Core rev: 0b4287dae51f7a4175c0ad3cadbec6cdf0b43866) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* crosstap: handle hyphenated x86_64 target archTom Zanussi2013-02-141-1/+1
| | | | | | | | | | | | | | systemtap_target_arch() should also translate x86-64 (hyphenated) into x86_64 for the -a param. Failing to do that causes systemtap to see an architecture mismatch and create a cloned session with a bogusly synthesized build directory path, and fails to compile the probe. Fixes [YOCTO #3756] (From OE-Core rev: d1d5cc19cb397ea3105578c3267fd86e0e8b7f55) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Fix typo in kvm capability detection in runqemuBjörn Stenberg2013-02-141-1/+1
| | | | | | | | (From OE-Core rev: 81b1298a9163f9de0574fe8a1c9ae49ea67fe5ff) Signed-off-by: Björn Stenberg <bjst@enea.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: set branches_base for list_property_values()Tom Zanussi2013-02-071-0/+4
| | | | | | | | | | | | | | yocto_bsp_list_property_values() is missing the context it needs to properly filter choicelists, so add it to the context object. Fixes [YOCTO #3233] (From meta-yocto rev: 064b15f76c5b52899f4c3fdef06412c3063062a5) (From meta-yocto rev: d381095eed24a426ea655c04279e23b13b1af34a) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: prepend includes in machine.scc files with machineTom Zanussi2013-02-076-12/+12
| | | | | | | | | | The names of the -user files were changed to have the machine prepended, but the includes weren't - fix the includes. (From meta-yocto rev: f56d24c04f00cfb2671e3f097f221d636ebb7943) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: qualify user files with machine nameBrian A. Lloyd2013-02-0542-87/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The bblayer abstraction makes it where multiple layers can be configured and used at the same time. Some layers make changes to support a specific machine, and should not have any affect when other machines are in use. For linux-yocto, all bsps are created with a user-config.cfg and user-config.cfg and user-patches.scc. This means that those files will be pulled from the first location found, which might correspond to files customized for a different machine. Instead of using the names user-config.cfg and user-patches.scc, I propose a machine specific name be used such as {{=machine}}user-patches.scc and {{=machine}}user-config.cfg. This would necessitate that all references changed to these new names, which would affect the yocto-bsp and yocto-kernel scripts. With this change, it would be possible to have multiple machine BSPs searched at the same time and to select which to build against by using a command like MACHINE=qmeux86 bitbake core-image-sato to override the default. Note many of the standard BSPs do not seem to suffer this problem as they do not use the common files user-config.cfg and user-patches.scc that the yocto-* scripts depend upon. Additions by Tom Zanussi: - renamed user-config.cfg to {{=machine}}-user-config.cfg everywhere - renamed user-patches.scc to {{=machine}}-user-patches.scc everywhere - added the user-config/patches SRC_URI items to the qemu -rt kernel recipes Fixes [YOCTO #3731] (From meta-yocto rev: b148d800773f3c2e6edeb4f05850b0291a8bb7d5) Signed-off-by: Brian A. Lloyd <brian.lloyd@familyhonor.net> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management: hide error message when one of possible layer ↵Martin Jansa2012-10-101-1/+1
| | | | | | | | | | | location doesn't exist * fixes [YOCTO #3116] (From OE-Core rev: bde88116d9d7e86ca7ecac4cf990689f972b0b1c) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Add BB_NO_NETWORK to BB_ENV_EXTRAWHITEOtavio Salvador2012-10-101-1/+1
| | | | | | | | | | This allows for use of bitbake in offline mode, but override it in command line. (From OE-Core rev: bcefd015fb163d9c382ae05a86569dbcfd3d736a) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: allow multiple unfs instances to run simultaneouslyScott Garman2012-10-102-4/+4
| | | | | | | | | | | | | | | A miscalculation in the way the port numbers of mountd and nfsd are created was causing conflicts when starting multiple instances of qemu using userspace nfs. Thanks to Rudolf Streif for proposing this fix! Fixes [YOCTO #1969] (From OE-Core rev: 94eef772c283170d19ba92c8de0054cd093fc487) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-export-rootfs: improve rpcbind error detectionScott Garman2012-10-101-9/+24
| | | | | | | | | | | mountd requires rpcbind or portmap. Check that one of these services is running before doing anything else, and report a user-friendly error when they are not found. (From OE-Core rev: 16d6ec51f4b976c9b86a8b6bf6251089df2d2732) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-export-rootfs: use consistent whitespaceScott Garman2012-10-101-47/+47
| | | | | | | (From OE-Core rev: b05185240669e0ae811a23620913b35ca99493fb) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: Fixed running QEMU with virtio error reportingCristian Iorga2012-10-031-6/+6
| | | | | | | | | | | | | | | | If vhost_net module is not properly installed, runqemu script will report the error and provide the user with a link to the guide. Also corrected small cosmetic issues in runqemu script messages. Also removed <> (read/write) check. Fixes [YOCTO #3184] (From OE-Core rev: f7365f62325189b0f9a9a1d440f11f2356c8f01d) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-buildenv-internal: Ensure we detect the SDK/ADT and error outRichard Purdie2012-10-021-0/+5
| | | | | | | | | | | | | | The SDK/ADT may ship with a python installed which may not have all the modules need for a bitbake build. We should therefore detect if its already present in the environment and error out in this case, asking the user to use a clean environment. This also removes the potential for any other conflict between the two. [YOCTO #2979] (From OE-Core rev: 9496d4cd77ae632251b4262b63be857fc4fcb31e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: remove 'test' options from user-config.cfgTom Zanussi2012-10-012-8/+0
| | | | | | | | | | A couple bsp templates have some options that were used for testing but aren't needed for any other reason - remove them. (From meta-yocto rev: dd3bbd04919f7cc69141f405ac95d736abddd637) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: use FILESEXTRAPATHS for xserver-xf86-config bbappendsTom Zanussi2012-10-014-11/+4
| | | | | | | | | | The xserver-xf86-config .bbappends are still using FILESPATH - update them to use FILESEXTRAPATHS as recommended by the Poky Reference Manual and BSP Developer's Guides. (From meta-yocto rev: 6aaef8eb9e95a46ab02ef038ae53c8e63eb04e09) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: fix dmaengine feature inclusionTom Zanussi2012-09-281-1/+1
| | | | | | | | | | | The cfg/dmaengine/dmaengine feature changed location to cfg/dmaengine in the 3.4 yocto kernel's meta branch. Add template code to include the appropriate version. (From meta-yocto rev: b650fcb7781e1c6af6254c98ae64d5ea81b46abc) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: make vfat feature inclusion conditional on kernel versionTom Zanussi2012-09-282-1/+7
| | | | | | | | | | | | | The linux-yocto-3.2 cfg/vfat feature changed location to cfg/fs/vfat in the 3.4 yocto kernel's meta branch. Add template code to include the appropriate version depending on kernel version. Fixes [YOCTO #3178]. (From meta-yocto rev: d574c56c51789ec56ff50518ac2057607740eaa8) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-internal: don't append an empty element to PATHScott Garman2012-09-281-1/+5
| | | | | | | | | | | | | Bitbake fails to run when an empty element exists in $PATH. Avoid creating this situation when $CROSSPATH is not set. This fixes bug [YOCTO #3101] (From OE-Core rev: 1f7f590369eaa76dc970c9cffd1f0db53ce08c00) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-find-native-sysroot: show bitbake errors to userScott Garman2012-09-281-10/+19
| | | | | | | | | | | | | Ran into another bug that was masked by hiding a bitbake error message. This catches this situation and displays the error to the user. Also includes whitespace fixes. (From OE-Core rev: 435ffeefe4a1df53335fd397ff404bed7deae2df) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management: hide error message when one of possible layer ↵Martin Jansa2012-09-271-1/+1
| | | | | | | | | | | location doesn't exist * fixes [YOCTO #3116] (From OE-Core rev: b02d334e0e6a19a1bf3550add68f5770a835c772) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* SDK: trap any IO errors in the relocate scriptLaurentiu Palcu2012-09-261-2/+12
| | | | | | | | | | | | | | | | If the files being relocated are already used by other processes the relocate script will fail with a traceback. This patch will trap any IO errors when opening such a file and gracefully report them to the user. Also change the exit code from 1 to -1 for a better adt-installer user experience (like pointing the user to the adt_installer.log). [YOCTO #3164] (From OE-Core rev: 26daec758b2eaeb208356d5aa8a9a191bd366751) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: work with tap device names that end with a colonScott Garman2012-09-242-2/+2
| | | | | | | | | | | | | On Fedora systems (and likely others), ifconfig returns interface names that end with a colon. Make sure we strip the colon off the tap device name before using it. This fixes [YOCTO #3028] (From OE-Core rev: 85ed217b603a86113dda11d952850e8ceed30795) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemux86-64: Support for KVM, paravirt and virtio addedCristian Iorga2012-09-211-2/+2
| | | | | | | | | | | | | | | KVM, paravirtualization and virtio drivers are now activated in runqemu using the kvm option flag for qemux86-64. Host CPU features are also exported to guest OS (Yocto Linux). Usage example: runqemu qemux86-64 core-image-x11 kvm Implements [YOCTO #2550]. (From OE-Core rev: cbb6431b3ee9128ea15c9ae0a19e7d2998ffc561) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemux86: Support for KVM, paravirt and virtio addedCristian Iorga2012-09-212-4/+26
| | | | | | | | | | | | | | | KVM, paravirtualization and virtio drivers are now activated in runqemu using the kvm option flag for qemux86. Host CPU features are also exported to guest OS (Yocto Linux). Usage example: runqemu qemux86 core-image-x11 kvm Implements [YOCTO #2550]. (From OE-Core rev: a35d03e2eb905de4eadc9c7df5b50bff1fb7f897) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: show bitbake errors to userScott Garman2012-09-211-2/+10
| | | | | | | | | | | | | | In certain edge cases, bitbake may fail to run and cause setup_tmpdir() within runqemu to fail, and not give the user a helpful error message. Catch this case and show the user the output of bitbake -e. This fixes [YOCTO #3112] (From OE-Core rev: 465d7b6e66b5a55706535e194b3e44e11ee542c6) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mkefidisk.sh: Add script to do an EFI install on the hostDarren Hart2012-09-211-0/+255
| | | | | | | | | | | | | | | | Sometimes it is convenient to prepare a bootable image from the host rather than using a live-image to install to a disk on the target. This script takes a live image as input, partitions a device, and performs the installation just as the installer would if run on the target. (From OE-Core rev: 7225c6739f9f1e51741a42437692868165aa1dfe) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Replace "echo -e" with "printf" to have the same behavior in dash or bashAndrei Gherzan2012-09-201-1/+1
| | | | | | | | | | | | | | | | | | | | oe-core removed the prerequisite to have sh as bash. POSIX doesn't define any options and furthermore allows 'echo -e' to be the default behavior. This means that in dash 'echo -e' will actually print '-e' and interpret backslashes by default. We use instead 'printf' builtin command with or without '\n' to simulate 'echo -e' or 'echo -n'. 'printf' needs format while 'echo' can be used without any arguments. So 'echo >' was replaced by 'printf "" >'. 'echo' without '-n' flag adds a new line by default so to keep the same behavior of two new lines while using 'echo "\n"', 'printf "\n\n"' is used. [YOCTO #3138] (From OE-Core rev: a19880ad10ccb5d7d909dcf9de5c3dc58a0ebcd3) Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/combo-layer: ensure we validate branch/revision on initPaul Eggleton2012-09-141-4/+7
| | | | | | | | | | | | | If both branch and last_revision are specified for a component when combo-layer init is run, ensure that the specified revision is actually on the specified branch and error out if not. Also ensure that the error message mentions the component. (From OE-Core rev: e498257ecbec94cec181d73bda57d44335b4dee0) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/combo-layer: use last_revision if specified in initPaul Eggleton2012-09-141-7/+13
| | | | | | | | | | | | | | | | If last_revision is specified for a component when running combo-layer init, then use that revision instead of the latest revision on the branch. Also, remove unnecessary git checkout during init since we specify the revision to all calls to git when dealing with the component repositories. Fixes [YOCTO #3040]. (From OE-Core rev: ff8277cd133e9a02b131977078cff61fa587a1af) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: Explicitly specify MACHINE when calling bitbakeKhem Raj2012-09-141-1/+1
| | | | | | | | | | | | | When using runqemu with distros outside oe-core then MACHINE may not be there in local.conf so use the one thats available in environment of runqemu which is actually the correct one. (From OE-Core rev: 5c3fec058a2d370fbb625901ca1822ce04927ac2) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts: change default ARM BSP to use xserver-xorg, not -liteRoss Burton2012-09-121-2/+2
| | | | | | | (From meta-yocto rev: 22cd22813a07c03f47810754a89916f629ce13cd) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: remove packagegroup-core-tools-profile.bbappendTom Zanussi2012-09-101-2/+0
| | | | | | | | | | | | The functionality previously added by these bbappends was already handled in task-core-tools-profile.bb (now packagegroup-core-tools-profile.bb), so remove this. (From meta-yocto rev: e999a6639a711f5c9a64c69d6b89fb478566d34a) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-09 08:00:59 +0000